Hybrid deployment of ephemeral scanners (as amended)

ABSTRACT

A cybersecurity scanner deployment system, comprising: at least one processor configured to: access a primary account maintained in a cloud environment; receive information defining a structure of the primary account, the structure including a plurality of assets, and the information excluding raw data of the primary account; deploy, inside the primary account or a secondary account for which trust is established with the primary account, at least one ephemeral scanner configured to scan at least one block storage volume and output metadata defining the at least one block storage volume, the output excluding raw data of the primary account; receive a transmission of the metadata from the at least one ephemeral scanner, excluding raw data of the primary account; analyze the metadata to identify cybersecurity vulnerabilities; correlate each of the cybersecurity vulnerabilities with one of the assets; and generate a report correlating the cybersecurity vulnerabilities with the assets.

PRIORITY

This application claims the benefit of U.S. Provisional Application No.63/180,048 filed on Apr. 26, 2021, the contents of which are herebyincorporated by reference.

TECHNICAL FIELD

Disclosed embodiments include new systems and methods for securing cloudinfrastructure to help meet compliance mandates, without disruptingbusiness operations in live environments.

BACKGROUND

Modern organizations typically depend on cloud infrastructure for datastorage and processing. Data storage and processing nodes, among otherthings, power today's electronic infrastructure. In contrast to earlynetwork-centric days, an organization may have little in the way of“on-prem” (on-premises) systems and may run its entire business throughsystems having shared resources. Such an infrastructure may be theentire inventory of cloud assets for an organization, including runningand stopped workloads of all types: virtual machines, containers,storage objects, load balancers, IAM (Identity and Access Management)configurations, and more. Organizations are searching for effective waysto scan their entire cloud estate to look for risks stemming fromvulnerabilities, misconfigurations, malware, lateral movement risk, weakand leaked passwords, and improperly secured PII.

The infrastructure of these organizations are plainly different than'90s-style physical servers running on bare metal. Existing agents andscanners from the on-prem days have been simply reused in cloudenvironments without reconfiguration. Before the cloud, it was requiredto secure physical hosts. That meant spending time installing multiplesecurity agents—one for each server. IP addresses were assigned tophysical assets and they seldom changed. Even then, however, agentintegration was tedious and coverage rarely reached 100% of assets. In acloud environment, scaling up and down is a frequent occurrence—possiblythousands of times per hour across multiple clouds—and all within aCl/CD pipeline that builds an organization's infrastructure. There arecontainers and virtual machines to contend with, and agents carry highoperational costs.

This causes problems of inefficiency and overuse of resources, includingexcess processor cycles on regular scans. In turn, such problems andinefficiencies can lead to a higher monetary cost for hosted resourcesas some cloud providers charge per processing cycle.

Relying on agents for security visibility in the cloud also hasdrawbacks. Visibility is limited to only those assets that are alreadyknown and accessible to an agent, requiring that such assets are capableof having the agent installed and maintained in the first place. Theassets also must have ongoing network connectivity to the backend,something that makes the development cycle inefficient as developerstend not to be inclined to deploy agents on virtual machines, incontainers, and in serverless configurations—let alone dealing withtheir never-ending maintenance—thus leading to insecure implementations.

An authenticated scan allows for direct host access using remoteprotocols such as SSH or RDP. The scanner uses a privileged account tolog in and determine how secure each host is from an inside vantagepoint. While authenticated scans can successfully discover potentialvulnerabilities, they are limited as they require a privileged accounton each scanned host. Furthermore, scans use significant systemresources during the test procedures and require opening ports that bythemselves pose a security risk.

An unauthenticated scan can only examine publicly visible informationand is not able to provide detailed information about assets. Itessentially acts as a friendly attacker. An unauthenticated scan caneasily miss identifying some assets and vulnerabilities, making it muchless effective. For example, a website at https://mydomain.com/emailcampaign not linked from a main website will not be scanned unless thescanner is manually configured. This can leave organizations exposed tovulnerabilities in areas where the scanner cannot reach.

While unauthenticated scanners act like an attacker, they often getstuck where a real attacker would not. For example, a CAPTCHA can easilyprevent automatic mechanisms (such as scanners) from registering. Butsuch techniques would not have any effect on a human attacker.

Cloud security posture managers (CSPMs) are scanning tools developedspecifically for the cloud. Rather than going inside the machine, a CSPManalyzes the cloud configuration itself for weaknesses. CSPMs are usedto discover, assess, and solve cloud misconfigurations but provideshallow coverage where cloud security is concerned because CSPMs havedifficulty detecting critical risks such as vulnerabilities, malware,and misconfigurations within the workloads themselves. Organizationschoosing to combine agent-based solutions with a CSPM end up gettingflooded with separate alerts that lack context which results in alertfatigue on behalf of security analysts.

Therefore, there is a need for improved security scanning systems thatsolve the problem with existing systems and are more adapted for use incloud infrastructures.

The foregoing background is for illustrative purposes and is notintended as a discussion of the scope of the prior art or an admissionof prior art.

SUMMARY

This summary is provided for the convenience of the reader to present abasic understanding of a few exemplary embodiments of this disclosure,and does not wholly define the breadth of the disclosure. This summaryis not an extensive overview of all contemplated embodiments and isintended to neither identify key or critical elements of all embodimentsnor to delineate the scope of any or all aspects. Its sole purpose is topresent some features of one or more embodiments in a simplified form asa prelude to the more detailed description presented later. Forconvenience, the term “embodiments” may be used herein to refer to oneor more features or combinations of features described herein. Adescription associated with an embodiment does not necessarily apply toall embodiments.

Embodiments of the present disclosure may deliver instant-on, workloadlevel visibility across cloud infrastructure assets without runningopcodes on the target scanned workloads, helping organizations to: (1)Detect risks such as vulnerabilities, malware, misconfigurations,lateral movement risk, and unsecured sensitive data; (2) See cloudinventory at every layer: infrastructure, operating system,applications, and data; (3) Discover and see previously missed assets.

Embodiments of the present disclosure may further use an out-of-bandprocess to reach cloud workloads through the runtime storage layer,combining this with information gathered from cloud provider APIs,including but not limited to K8S APIs.

DRAWINGS

The drawings and figures contained herein are a part of thisspecification, illustrate several embodiments consistent with thedisclosure and, together with the description, serve to explainprinciples of the disclosure.

FIG. 1 is a schematic block diagram illustrating an exemplary embodimentof a network including computerized systems, consistent with disclosedembodiments.

FIG. 2A is a schematic block diagram illustrating an exemplaryembodiment of a process for integration, scanning, assessment,analyzing/reporting, and change reviewing, consistent with disclosedembodiments.

FIG. 2B is a schematic block diagram illustrating an exemplaryembodiment of a process for integration, consistent with disclosedembodiments.

FIG. 2C is a schematic block diagram illustrating an exemplaryembodiment of a process for scanning/mapping, consistent with disclosedembodiments.

FIG. 2D is a schematic block diagram illustrating an exemplaryembodiment of a process for assessment, consistent with disclosedembodiments.

FIG. 3 is a block diagram of method for insight extraction, consistentwith disclosed embodiments.

FIG. 4 depicts a cybersecurity system performing a side scanningfunction to protect against potential vulnerabilities, consistent withdisclosed embodiments.

FIG. 5 of the disclosed embodiments describes a method of operating acybersecurity system performing a side scanning function to protectagainst potential vulnerabilities, consistent with disclosedembodiments.

FIG. 6 is a block diagram of method for risk prioritization, consistentwith disclosed embodiments.

FIG. 7 is a block diagram illustrating an exemplary process of cybersecurity scanning for a cloud environment, consistent with the disclosedembodiments.

FIG. 8 is a schematic block diagram illustrating an exemplary embodimentof a system for performing visualization of forward and backward facingthreats, consistent with the disclosed embodiments.

FIG. 9 is a block diagram illustrating an exemplary process of matchingkeys with compute resources in a cloud environment, consistent with thedisclosed embodiments.

FIG. 10 is a block diagram of a method for deployment of ephemeralscanners, consistent with disclosed embodiments.

FIG. 11 represents a schematic block diagram illustrating an exemplaryembodiment of a method for providing a dashboard aggregating riskinformation, consistent with disclosed embodiments.

FIG. 12 is a schematic block diagram illustrating an exemplaryembodiment of a visual representation of displaying aggregatedcybersecurity risk information, consistent with disclosed embodiments.

FIG. 13 is a schematic block diagram illustrating an exemplaryembodiment of a visual representation of a flow path for aggregated riskinformation, consistent with disclosed embodiments.

DETAILED DESCRIPTION

Exemplary embodiments are described with reference to the accompanyingdrawings. The figures are not necessarily drawn to scale. While examplesand features of disclosed principles are described herein,modifications, adaptations, and other implementations are possiblewithout departing from the spirit and scope of the disclosedembodiments. For example, with this detailed description provides a fewexamples, these implementations are provided as examples only and arenot restrictive of the claim concepts that follow or any of thedescriptions herein. Also, the words “comprising,” “having,”“containing,” and “including,” and other similar forms are intended tobe equivalent in meaning and be open ended in that an item or itemsfollowing any one of these words is not meant to be an exhaustivelisting of such item or items or meant to be limited to only the listeditem or items. It should also be noted that as used herein and in theappended claims, the singular forms “a,” “an,” and “the” include pluralreferences unless the context clearly dictates otherwise.

In the following description, various working examples are provided forillustrative purposes. However, it is to be understood that the presentdisclosure may be practiced without one or more of these details.

It is intended that one or more aspects of any mechanism may be combinedwith one or more aspect of any other mechanisms, and such combinationsare within the scope of this disclosure.

Various embodiments are described herein with reference to a system,method, device, or computer readable medium. It is intended that thedisclosure of one is a disclosure of all. For example, it is to beunderstood that disclosure of a computer readable medium describedherein also constitutes a disclosure of methods implemented by thecomputer readable medium, and systems and devices for implementing thosemethods, via for example, at least one processor. It is to be understoodthat this form of disclosure is for ease of discussion only, and one ormore aspects of one embodiment herein may be combined with one or moreaspects of other embodiments herein, within the intended scope of thisdisclosure.

Embodiments described herein may refer to a non-transitory computerreadable medium containing instructions that when executed by at leastone processor, cause the at least one processor to perform a method.Non-transitory computer readable medium may include any medium capableof storing data in any memory in a way that may be read by any computingdevice with a processor to carry out methods or any other instructionsstored in the memory. The non-transitory computer readable medium may beimplemented as hardware, firmware, software, or any combination thereof.Moreover, the software may preferably be implemented as an applicationprogram tangibly embodied on a program storage unit or computer readablemedium consisting of parts, or of certain devices and/or a combinationof devices. The application program may be uploaded to, and executed by,a machine having any suitable architecture. Preferably, the machine maybe implemented on a computer platform having hardware such as one ormore central processing units (“CPUs”), a memory, and input/outputinterfaces. The computer platform may also include an operating systemand microinstruction code. The various processes and functions describedin this disclosure may be either part of the microinstruction code orpart of the application program, or any combination thereof, which maybe executed by a CPU, whether or not such a computer or processor isexplicitly shown. In addition, various other peripheral units may beconnected to the computer platform such as an additional data storageunit and a printing unit. Furthermore, a non-transitory computerreadable medium may be any computer readable medium except for atransitory propagating signal.

Memory employed herein may include a Random Access Memory (RAM), aRead-Only Memory (ROM), a hard disk, an optical disk, a magnetic medium,a flash memory, other permanent, fixed, volatile or non-volatile memory,or any other mechanism capable of storing instructions. The memory mayinclude one or more separate storage devices collocated or disbursed,capable of storing data structures, instructions, or any other data. Thememory may further include a memory portion containing instructions forthe processor to execute. The memory may also be used as a workingscratch pad for the processors or as a temporary storage.

Some embodiments may involve at least one processor. A processor may beany physical device or group of devices having electric circuitry thatperforms a logic operation on input or inputs. For example, the at leastone processor may include one or more integrated circuits (IC),including application-specific integrated circuit (ASIC), microchips,microcontrollers, microprocessors, all or part of a central processingunit (CPU), graphics processing unit (GPU), digital signal processor(DSP), field-programmable gate array (FPGA), server, virtual server, orother circuits suitable for executing instructions or performing logicoperations. The instructions executed by at least one processor may, forexample, be pre-loaded into a memory integrated with or embedded intothe controller or may be stored in a separate memory.

In some embodiments, the at least one processor may include more thanone processor. Each processor may have a similar construction, or theprocessors may be of differing constructions that are electricallyconnected or disconnected from each other. For example, the processorsmay be separate circuits or integrated in a single circuit. When morethan one processor is used, the processors may be configured to operateindependently or collaboratively. The processors may be coupledelectrically, magnetically, optically, acoustically, mechanically or byother means that permit them to interact.

Consistent with the present disclosure, disclosed embodiments mayinvolve a network. A network may constitute any type of physical orwireless computer networking arrangement used to exchange data. Forexample, a network may be the Internet, a private data network, avirtual private network using a public network, a Wi-Fi network, a LANor WAN network, and/or other suitable connections that may enableinformation exchange among various components of the system. In someembodiments, a network may include one or more physical links used toexchange data, such as Ethernet, coaxial cables, twisted pair cables,fiber optics, or any other suitable physical medium for exchanging data.A network may also include a public switched telephone network (“PSTN”)and/or a wireless cellular network. A network may be a secured networkor unsecured network. In other embodiments, one or more components ofthe system may communicate directly through a dedicated communicationnetwork. Direct communications may use any suitable technologies,including, for example, BLUETOOTH™, BLUETOOTH LE™ (BLE), Wi-Fi, nearfield communications (NFC), or other suitable communication methods thatprovide a medium for exchanging data and/or information between separateentities.

Certain embodiments disclosed herein may also include a computing devicefor cloud cybersecurity, the computing device may include processingcircuitry communicatively connected to a network interface and to amemory, wherein the memory contains instructions to be executed. Thecomputing devices may be devices such as mobile devices, desktops,laptops, tablets, or any other devices capable of processing data. Suchcomputing devices may include a display such as an LED display,augmented reality (AR), virtual reality (VR) display.

“Software” as used herein refers broadly to any type of instructions,whether referred to as software, firmware, middleware, microcode,hardware description language, or otherwise. Instructions may includecode (e.g., in source code format, binary code format, executable codeformat, or any other suitable format of code). The instructions, whenexecuted by the one or more processors, may cause the processing systemto perform the various functions described in further detail herein.

The one or more processors may be implemented with any combination ofgeneral-purpose microprocessors, microcontrollers, digital signalprocessors (DSPs), field programmable gate array (FPGAs), programmablelogic devices (PLDs), controllers, state machines, gated logic, discretehardware components, dedicated hardware finite state machines, or anyother suitable entities that can perform calculations or othermanipulations of information.

Aspects of this disclosure may provide technical solutions to challengesassociated with cloud cybersecurity. Disclosed embodiments includemethods, systems, devices, and computer-readable media. For ease ofdiscussion, a system is described below with the understanding that thedisclosed details may equally apply to methods, devices, andcomputer-readable media.

Embodiments of the present disclosure include technology referred to as“SideScanning.” In contrast to some existing systems and techniques,these embodiments may provide a distinct advantage because thetechnology does not necessarily require entering into each workload toinspect data. Rather, some embodiments use an out-of-band process toreach cloud workloads through a runtime storage layer, combining thiswith metadata gathered from API provided through a cloud serviceprovider's system, thus providing visibility of cloud environments bothat a low level and with context, without the requirement for an agent ornetwork scanner.

FIG. 1 is a schematic block diagram 100 illustrating an exemplaryembodiment of a network including computerized systems, consistent withthe disclosed embodiments. Diagram 100 includes user device 102, network105, and cloud infrastructure 106.

Cloud infrastructure 106 includes scanning system 101, databases103A-103D, virtual machines 107A-107D, databases 109A-109D, storage111A-111D, keystores 113A-113D, and load balancer 115. While particularnumbers and arrangements of devices, systems, and connections, aredepicted in exemplary FIG. 1, in some embodiments, each of the devices,systems, or connections may be omitted, duplicated, or modified. Forexample, in some embodiments, databases 109A-109D may exist as only asingle database; in other embodiments, cloud infrastructure 106 mayexist as one or more distinct or combined infrastructures (e.g.,operated by the same or different cloud services). In some embodiments,scanning system 101 and/or databases 103A-103D may be part of cloudinfrastructure 106 (and may be connected to the various other systemsand devices in cloud infrastructure 106); in other embodiments, scanningsystem 101 and/or databases 103A-103D may be separate from cloudinfrastructure 106 (e.g., connected to the systems and devices in cloudinfrastructure 106 through network 105).

Scanning system 101, in some embodiments, may include one or morecomputer systems. Each of the one or more computer systems may includememory storing instructions and at least one CPU configured to executethose instructions to perform operations as discussed herein. In someembodiments, the instructions cause the CPU to perform scanningoperations. In some embodiments, scanning system 101 may perform ascanning operation on one or more workloads (e.g., systems, devices,resources, etc.) in cloud infrastructure 106.

User device 102, in some embodiments, may include a mechanism operatedby a user to control scanning system 101. For example, in someembodiments, user device 102 may be any of a personal computer, aserver, a thin client, a tablet, a personal digital assistant, asmartphone, a kiosk, or any other mechanism enabling data input. Userdevice 102 may be operated to instantiate functionality, access data, orotherwise interact with scanning system 101 via network 105, asdescribed herein.

Databases 103A-103D include data stores for use by scanning system 101.In some embodiments, one or more of databases 103A-103D may beimplemented as a NoSQL database, a relational database, a clouddatabase, a columnar database, a wide column database, a key-valuedatabase, an object-oriented database, a hierarchical database, or anyother kind of database. In some embodiments, one or more of databases103A-103D may be implemented as flat file stores, data stores, or othernon-database storage systems. In some embodiments, databases 103A-103Dmay be implemented using one or more of ElasticCache, ElasticSearch,DocumentDb, DynamoDB, Neptune, RDS, Aurora, Redshift clusters, Kafkaclusters, or EC2 instances.

Network 105 may be implemented as one or more interconnected datanetworks. For example, network 105 may include one or more of any typeof network (including infrastructure) that provides communications,exchanges information, and/or facilitates the exchange of information,such as the Internet, a Local Area Network, a near field communication(NFC) network, or other suitable connection(s) that enables the sendingand receiving of information between the components of system 100.Network 105 may be implemented using wireless connections, wiredconnections, or both. In some embodiments, one or more components ofsystem 100 can communicate through network 105. In some embodiments, oneor more components of system 100 may communicate directly through one ormore dedicated communication links. While particular devices and systemsare shown as connected to network 105, in some embodiments, more orfewer devices and systems may be connected to network 105.

Cloud infrastructure 106 may be implemented as a set of devices andsystems offered by a single cloud service provider. For example, cloudinfrastructure 106 may comprise devices and systems that are part ofAmazon Web Services, Microsoft Azure, Google Cloud Platform, IBM Cloud,Alibaba Cloud, or any other cloud platform provider. In someembodiments, one or more of the devices and systems in cloudinfrastructure may require authentication or other identity validationfor access. For example, to access virtual machine 107A, a user may berequired to enter a password or provide a key. Systems (e.g., scanningsystem 101 or user device 102) may administer or interact with cloudinfrastructure 106 using a cloud service provider's system (notpictured).

Virtual machines 107A-107D may include one or more devices and systemsthat implement a virtualized/emulated version of a computer. A virtualmachine may be implemented as an emulated version of acomputer—including an operating system, memory, storage, graphicsprocessing—such that it can be indistinguishable from a standard(non-virtual) machine to a running program. A computer system, referredto as a “host,” may operate virtual machines 107A-107D, referred to as“guests,” by dividing the resources of the host between the virtualmachines such that each virtual machine is isolated from one another.This means that in some embodiments, one virtual machine, and theoperating system(s) and application(s) running thereon, is only able toaccess the resources that are allocated to that virtual machine andcannot access resources allocated to other virtual machines. Forexample, if a host has 32 gigabytes of random access memory (RAM), andis hosting three virtual machines, the host may segment 8 gigabytes ofRAM to each virtual machine such that each virtual machine may onlyaccess data in that 8 gigabytes of RAM and not any of the other 24gigabytes. Examples of commercial virtual machine software and servicesinclude VMWare Workstation, VMWare Server, VMWare ESXi, VirtualBox,Parallels Desktop, Parallels RAS, Amazon Machine Image, Amazon ECS,Kubernetes, Microsoft Hyper-V, and Xen.

Databases 109A-109D may include data stores for use by devices andsystems in cloud infrastructure 106. In some embodiments, one or more ofdatabases 109A-109D may be implemented as a NoSQL database, a relationaldatabase, a cloud database, a columnar database, a wide column database,a key-value database, an object-oriented database, a hierarchicaldatabase, or any other kind of database. In some embodiments, one ormore of databases 109A-109D may be implemented as flat file stores, datastores, or other non-database storage systems. In some embodiments,databases 109A-109D may be implemented using one or more ofElasticCache, ElasticSearch, DocumentDb, DynamoDB, Neptune, RDS, Aurora,Redshift clusters, Kafka clusters, or EC2 instances. Databases 109A-109Dmay store data usable by devices or systems in cloud infrastructure 106.The data, in some embodiments, may include e-commerce data (e.g.,shipments, orders, inventory), media data (e.g., pictures, movies,streaming data), financial data (e.g., banking data, investment data),or other data.

Storage 111A-111D may include storage systems for use by devices andsystems in cloud infrastructure 106. In some embodiments, one or more ofstorage 111A-111D may be implemented as a hard drive, a RAID array,flash memory, optical storage, or any other kind of storage. Each of111A-111D may include one or more filesystems (e.g., Amazon Elastic FileSystem, GlusterFS, Google File System, Hadoop Distributed File System,OpenZFS, S3, Elastic Block Storage).

In some embodiments, systems and devices of cloud infrastructure 106 mayuse databases 109A-109D to store data that is accessed frequently(where, for example, access is required within a few milliseconds), andmay use storage 111A-111D to store data that is accessed less frequently(where, for example, access is required within a few minutes or hours).

Keystores 113A-113D may include systems storing keys for accessing dataand functionality. For example, to access certain data or systems, asystem may require the use of passwords or keys in keystores 113A-113Dfor authentication. The data and functionality that the keys grantaccess to may be part of cloud infrastructure 106 or may be separatefrom cloud infrastructure 106. For example, keystores 113A-113D mayinclude systems that store public and private keys (e.g., for use viaSSH), may store passwords (e.g., login information for websites orprograms), may store tokens (e.g., one-time passcodes), or the like. Insome embodiments, keystores 113A-113D may be implemented as one or moreof Amazon Web Services KMS, Azure Key Vault, or Google KMS.

Load balancer 115 may include one or more systems that balance incomingrequests between the different systems and devices of cloudinfrastructure 106. For example, load balancer 115 may be configured todetermine usage (e.g., processor load, used storage capacity) of systemsor devices in cloud infrastructure 106 to assist in determining where toroute an incoming request from network 105 to store data, performprocessing, or retrieve data.

Load balancer 115 may be configured to receive an incoming request fromuser device 102. Upon receipt of the request, load balancer 115 mayconsult a data store (part of or separate from load balancer 115; notpictured) to determine usage or forecasted usage of various systems ordevices in cloud infrastructure 106, and may forward the request to thesystems or devices having the lowest usage or forecasted usage.

FIG. 2A is a schematic block diagram illustrating an exemplaryembodiment of a process 200 for integration, scanning, assessment, andreview, consistent with the disclosed embodiments. In some embodiments,the steps in FIG. 2A are executed using software and hardware ofscanning system 101. In some embodiments, the steps in FIG. 2A may beperformed in an order other than those depicted in FIG. 2A. In someembodiments, steps may also be omitted, repeated, or modified. In someembodiments, information gathered in one step of FIG. 2A may be used toprovide context or other information for use in another step of FIG. 2A.In other embodiments, the steps in FIG. 2A may be executed by otherdevices.

Process 200 begins with step 201. In step 201, scanning system 101 mayexecute a process of integration. The integration process may beperformed by scanning system 101 with cloud infrastructure 106. In someembodiments, the integration process includes creating a connectionbetween an account on scanning system 101 and an account on cloudinfrastructure 106. The process of integration in step 201 may, in someembodiments, be implemented as described below with respect to FIG. 2B.

In step 203, scanning system 101 may execute a process ofscanning/mapping. The scanning/mapping process may be performed byscanning system 101 with cloud infrastructure 106. In some embodiments,the scanning and mapping process may include analyzing data relating tocloud infrastructure 106 using scanning system 101, by reading cloudinfrastructure 106 through the connection made in step 201 and generatea “map” (e.g., a data structure or data collection) representing systemsand devices in cloud infrastructure 106. The process of scanning andmapping in step 203 may, in some embodiments, be implemented asdescribed below with respect to FIG. 2C.

In step 205, scanning system 101 may execute a process of assessing. Theassessing process may be performed by scanning system 101. In someembodiments, the assessing process may include reviewingvulnerabilities, infrastructure, interconnections, data, and otherinformation, using scanning system 101. The process of assessing in step205 may, in some embodiments, be implemented as described below withrespect to FIG. 2D.

In step 207, scanning system 101 may execute a process ofanalyzing/reporting. The analyzing/reporting may be performed byscanning system 101. In some embodiments, the change reviewing processcomprises scanning system 101 scanning cloud infrastructure 106 again todetermine the differences between an earlier observed snapshot of cloudinfrastructure 106 and the current state thereof. In some embodiments,scanning system 101 may analyze information (e.g., steps 203 and/or 205)to generate reports. The reports may list what each vulnerability is,where it is located, and its priority. In this way, security engineersand DevOps teams may be able to easily assess how to best allocate theirtime and attention.

In some embodiments, analyzing/reporting in step 207 may includescanning system 101 combining conclusions from different environmentalperspectives (e.g., metadata) into a single model. For example, scanningsystem 101 may map the running services on cloud infrastructure 106 andconsider collected vulnerability data. Scanning system 101, in someembodiments, may generate a visualization of the map for review, listingwhere the vulnerabilities are on a two-dimensional graphicalrepresentation of cloud infrastructure 106.

In some embodiments, scanning system 101 may indicate in the map whetheran asset (e.g., a system or device) is Internet-facing and easilyaccessible to attackers, exposed only to internal assets or if it isprivate altogether (and may be less critical). For example, based on thecontextual map, scanning system 101 may perform a “forward” analysis ofthe specific asset under identification to identify at least onepossible Internet-originating attack vector to the asset. Alternativelyor additionally, scanning system 101 may perform a “backward” analysisof the specific asset to identify exposure risk to assets downstream ofthe specific asset, wherein the downstream exposure risk includes anidentification of an exposed asset, an entry point to the exposed asset,and lateral movement risks associated with the exposed asset. Bothbackward and forward analysis can be recursively, for one or more hops,Scanning system 101 may present these analyses to a user via graphicaluser interface or expose them via an API.

As one example, scanning system 101 may determine a vulnerability in aweb service. In some embodiments, scanning system 101 may score thevulnerability as: high risk if the web service is connected to theInternet (e.g., has at least one public port forwarded through afirewall to the web service, is able to be accessed through a loadbalancer, is able to be accessed via reverse proxy); medium risk if theweb service is only accessible internally (e.g., because of firewallconfiguration); and low risk if access to the web server is blocked by aconfiguration of cloud infrastructure 106. As another example, if amachine is stopped (e.g., turned off, not running, not connected), avulnerability, but one that is less likely to be exploited because themachine isn't running. This affects its risk score and other mitigatingfactors.

In step 209, scanning system 101 may execute a process of changereviewing. The change reviewing may be performed by scanning system 101.In some embodiments, the change reviewing process may include scanningsystem 101 scanning cloud infrastructure 106 again to determine thedifferences between an earlier observed snapshot of cloud infrastructure106 and the current state thereof.

In some embodiments, scanning system 101 may monitor cloud change, or“delta,” logs (e.g., Cloud event logs such as AWS CloudTrail, monitoringa network-related change in state, a trust-related change in state, or adisk configuration-related change in state in at least one of theprimary asset group or a secondary asset group) and contextualizeassociated risks discovered within a customer cloud account. In someembodiments, scanning system 101 may generate a new map of assets basedon a review of all systems or devices in cloud infrastructure 106 (e.g.,as described above with respect to step 203), and compare the new map tothe map generated earlier in step 203 to determine which assets havechanged. In some embodiments, this comparison may require comparingdata, metadata, network connections, software configurations, firewallconfigurations, or any other aspects related to cloud infrastructure106, including, for example, determining new assets that are created orassets for which their configuration has changed.

After step 209, as depicted in FIG. 2A, process 200 may return to step205. Scanning system 101 may then perform step 205 again. In someembodiments, steps 205, and 207 may be performed only on the devices orsystems that have experienced a change that was detected by step 209. Insome embodiments, process 200 may return to step 203 after step 209.

FIG. 2B is a schematic block diagram illustrating an exemplaryembodiment of a process 210 for integration, consistent with thedisclosed embodiments. In some embodiments, the steps in FIG. 2B areexecuted using software and hardware of scanning system 101.Integration, in some embodiments, is a process for creating a trustrelationship between scanning system 101 and cloud infrastructure 106.

In some embodiments, the steps in FIG. 2B may be performed in an orderother than those depicted in FIG. 2B. In some embodiments, steps mayalso be omitted, repeated, or modified. In some embodiments, informationgathered in one step of FIG. 2B may be used to provide context or otherinformation for use in another step of FIG. 2B. In other embodiments,the steps in FIG. 2B may be executed by other devices.

Process 210 may begin with step 211 to initiate a connection to cloudinfrastructure 106. In step 211, scanning system 101 may send a messageto user device 102 instructing a user to authenticate, or log in, to acloud service provider's system operating cloud infrastructure 106. Forexample, the user may use a username, password, one-time password,two-factor authentication, or any other authentication mechanism to gainaccess to a cloud service provider's system.

Concurrently with or after the first message, scanning system 101 maysend a second message to user device 102, instructing the user togenerate a role. The second message may include instructions for theuser to follow to generate the role. In step 213, a user may provide(e.g., via a keyboard at user device 102) a role definition to the cloudservice provider's system.

In some embodiments, the role definition includes read-only permissionsand permissions to read a block storage layer (containing block storagevolumes). In some embodiments, scanning system 101 provides a roleformation template (e.g., an Amazon Web Services CloudFormationTemplate) for use with cloud infrastructure 106 to create the necessaryrole. In step 213, the user may utilize user device 102, for example, bycopying and pasting a URL of the template, downloading and uploading thetemplate to the cloud service provider's system, or selecting thetemplate from a list of templates.

In step 215, the cloud service provider's system may generate a string(e.g., a “key” or “resource name”) for use by scanning system 101. Insome embodiments, this string may be used to enable access by scanningsystem 101 to the workload of cloud infrastructure as permitted by thegenerated role. A user using user device 102 may copy the string andpaste it into a user interface presented by scanning system 101 on userdevice 102. Other aspects of transmitting this string to scanning system101 are possible as well.

In step 217, scanning system 101 determines that it is able to accesscloud infrastructure 106. For example, scanning system 101 may attemptto perform a command such as authenticating to cloud infrastructure 106using the string received in step 215 or attempting to perform a commandusing cloud infrastructure (e.g., requesting a listing of files storedon storage 111A). Once scanning system 101 determines that it is able toaccess cloud infrastructure 106, the process may return to FIG. 2A andstep 203.

FIG. 2C is a schematic block diagram illustrating an exemplaryembodiment of a process 220 for scanning/mapping, consistent with thedisclosed embodiments. In some embodiments, the steps in FIG. 2C areexecuted using software and hardware of scanning system 101. In someembodiments, the steps in FIG. 2C may be performed in an order otherthan those depicted in FIG. 2C. In some embodiments, steps may also beomitted, repeated, or modified. In some embodiments, informationgathered in one step of FIG. 2C may be used to provide context or otherinformation for use in another step of FIG. 2C. In other embodiments,the steps in FIG. 2C may be executed by other devices.

Process 220 may begin with step 221 where scanning system 101 initiatesa process to access keys, such as those keys stored in keystores113A-113D. Scanning system 101 may utilize the string (e.g., a key orresource name) received in process 210 to authenticate in order toretrieve keys stored in keystores 113A-113D. Once authenticated,scanning system 101 may access one, some, or all keys stored inkeystores 113A-113D. In some embodiments, step 221 may compriseutilizing pre-established trust relationships, such as AWS trustpolicies, instead of creating a new relationship.

In step 223, scanning system 101 may generate a “snapshot” of devicesand systems in cloud infrastructure 106. In some embodiments, generatinga snapshot may include reading devices and systems in cloudinfrastructure, such as storage 111A-111D, databases 109A-109D, andvirtual machines 107A-107D, and copying the information read from thosedevices and systems to storage at scanning system 101. Generating asnapshot, in some embodiments, may include recording a reference countto data blocks in one or more of storage 111A-111D, databases 109A-109D,and virtual machines 107A-107D, and copying each block them like a copyand write operation. In some embodiments, scanning system 101 maygenerate an Elastic Block Storage snapshot in step 223.

In some embodiments, scanning system 101 uses one or more keys retrievedfrom keystores 113A-113D to encrypt “snapshots” of cloud infrastructure.

In step 225, scanning system 101 may apply “tags” to the snapshot. Thisprocess may include, in some embodiments, adding information to thesnapshot to identify the snapshot as being associated with scanningsystem 101. Scanning system 101, in some embodiments, may be configuredto delete only snapshots with the associated tags.

In step 227, scanning system 101 may generate a map of cloudinfrastructure 106. In some embodiments, this map may be in a form ofgraph: a plurality of interconnected vectors connecting the plurality ofsystems and devices, based on the networking configuration. Scanningsystem 101, or other devices, may traverse the map to identify vectorsoriginating in the Internet and reaching the devices and systems incloud infrastructure 106. In some embodiments, generating the map mayinclude enumerating Internet-accessible services that are capable ofserving as an Internet proxy. In some embodiments, a user may controlscanning system 101 (e.g., via user device 102) to display the map on agraphical user interface.

In some embodiments, generating the map may include enumeratingproperties of all assets, including: virtual machines 107A-107D,databases 109A-109D, storage 111A-111D, keystores 113A-113D, loadbalancer 115, log files or databases, API gateway resources, API gatewayREST APIs, Autoscaling groups, CloudTrail logs, CloudFront services,volumes, snapshots, VPCs, subnets, route tables, network ACLs, VPCendpoints, NAT gateways, ELB and ALB, ECR repositories, ECS clusters,services, and tasks, EKS, S3 bucket and Glacier storage, SNS topics, IAMroles, policies, groups, users, KMS keys, and Lambda functions. In someembodiments, generating the map in step 227 may further includeanalyzing devices or systems for a subset of risk related situations,including determinations of compromise situations (e.g., where anattacker has already gained access), imminent compromise situations(e.g., a known attack vector exists and can be used, such as a datastore that is exposed to the public Internet without authentication),hazardous situations (e.g., a serious security implication, but no fullattack vector exists), or informational situations (e.g., when storage111A-111D has a limited amount of free space, or an unexploitablevulnerability exists).

Generating the map in step 227 may include recording information such aregion identifier, site identifier, datacenter identifier, physicaladdress, network address, workload name, or any other identifier whichmay be acquired via an API provided through a cloud service provider'ssystem.

In step 229, scanning system 101 may provide alerts, e.g., to userdevice 102, indicating any situations found during the process ofgenerating the map. For example, scanning system 101 may send one ormore of an email, a popup alert, a text message, or other notificationto user device 102.

After performing step 229, the process may return to FIG. 2A and step205.

FIG. 2D is a schematic block diagram illustrating an exemplaryembodiment of a process 230 for assessing, consistent with the disclosedembodiments. In some embodiments, the steps in FIG. 2D are executedusing software and hardware of scanning system 101. In otherembodiments, the steps in FIG. 2D may be executed by other devices. Insome embodiments, scanning system 101 may execute the steps in FIG. 2Dagainst a snapshot created in step 223 of FIG. 2C and stored at scanningsystem 101. In some embodiments, the steps in FIG. 2D may be performedin an order other than those depicted in FIG. 2D. In some embodiments,steps may also be omitted, repeated, or modified. In some embodiments,information gathered in one step of FIG. 2D may be used to providecontext or other information for use in another step of FIG. 2D.

Process 230 begins with step 231. In step 231, scanning system 101 mayperform a step of vulnerability scanning. In some embodiments, step 231comprises extracting everything in the snapshot, including operatingsystem packages, installed software applications, libraries, and programlanguage libraries such as Java archives, Python packages, Go modules,Ruby gems, PHP packages, and Node.js modules, or other softwareapplications.

In some embodiments, step 231 may determine library versions, softwareversions, and other identifying characteristics of software andoperating systems in the snapshot. Scanning system 101 may then try tomatch them to known vulnerabilities stored in a vulnerability database(e.g., one of databases 103A-103D). The vulnerability database, in someembodiments, may include vulnerability data from: NVD, WPVulnDB,US-CERT, Node.js Security Working Group, OVAL—Red Hat, Oracle Linux,Debian, Ubuntu, SUSE, Ruby Advisory Database, JVN, Safety DB(Python),Alpine secdb, PHP Security Advisories Database, Amazon ALAS, RustSecAdvisory Database, Red Hat Security Advisories, Microsoft MSRC, KB,Debian Security Bug Tracker, Kubernetes security announcements, ExploitDatabase, Drupal security advisories, JPCERT. The vulnerability databasemay also include other vulnerability data (including, e.g.,manually-added vulnerability data or vulnerability sources not listedabove).

In step 233, scanning system 101 may perform a step of configurationscanning. In step 233, scanning system 101 may gather configurationinformation—such as a list of users of each system or device (e.g.,virtual machines 107A-D), each system's or device's services, passwordhashes, and application-specific configurations for software/servicessuch as Apache, Nginx, SSH, and other services. In some embodiments,scanning system 101 may perform a first analysis on all informationcollected in step 233 to remove sensitive information (e.g., socialsecurity numbers, passwords, birthdates) before proceeding to review theconfiguration information. In some embodiments, step 233 may compriseverifying adherence of the systems or devices in cloud infrastructure106 to standards or benchmarks established by an external entity, suchas the Center for Internet Security.

In some embodiments, scanning system 101 may perform a benchmarkingprocess to detect misconfigurations of any services based on theinformation gathered in step 233. For example, scanning system 101 maydetermine the software version of each service and examine it againstknown vulnerabilities (e.g., stored in database 103A).

In some embodiments, scanning system 101 may determine bugs or otherconfiguration risks that might only be exploitable from internalmachines, because such bugs and risks can facilitate an attacker'slateral movement.

In some embodiments, scanning system 101 may evaluate networkmisconfigurations and their implications. Scanning system 101 may querydevices and systems capable of routing traffic (e.g., load balancer 115,routers, switches, firewalls, and proxies) using an API provided througha cloud service provider's system to determine network configurations,and may evaluate them against known problematic configurations or otherconfigurations.

In step 235, scanning system 101 may perform a step of malware scanning.In some embodiments, scanning system 101 may perform malware scanningacross all filesystems in the snapshot (e.g., gathered from virtualmachines 107A-107D or storage 111A-111D). Scanning system 101 may usemultiple malware scanning software solutions to perform a malware scanagainst the filesystems, including one sourced from another vendor, suchas bucketAV, Trend Micro Cloud One, Sophos Cloud Optix, CrowdstrikeFalcon CWP, or others. In some embodiments, malware scanning in step 235comprises utilizing signatures, heuristics, or sandboxing capabilitiesto deduce whether there is an infection on the machine.

In step 237, scanning system 101 may perform a step of lateral movementscanning. An attacker who establishes a network foothold usuallyattempts to move laterally from one resource to another in search ofrich targets such as valuable data. Stolen passwords and keys unlockaccess to servers, files, and privileged accounts. In some embodiments,scanning system 101 may gather keys from each scanned system or device(e.g., virtual machines 107A-107D or storage 111A-111D). In someembodiments, scanning system 101 searches for passwords, scripts, shellhistory, repositories, or other data that may contain passwords, cloudaccess keys, SSH keys, or other key/password/access information thatprovide unchecked access to important resources. In some embodiments,scanning system 101 searches for such keys/passwords/access informationand calculates a “hash” (a mathematical fingerprint) of each string.Scanning system 101 then attempts to match the hashed strings to hashesof strings that that are stored on different systems or devices. Thiswill be used to detect the potential lateral movement between assets.

In step 239, scanning system 101 may perform a step of key/passwordscanning. As one example situation, suppose there is a weak orunprotected password stored (in plain text) in storage 111A. Forexample, if a personal email account has been compromised, the passwordsmay be known about in advance. Scanning system 101 may search thesnapshot for similar usernames or login names, and, either using knowndictionaries or the account owner's previously leaked passwords (storedin, e.g., database 103A), may attempt to login to one or more systems ordevices in cloud infrastructure 106, and may record the result thereof.

In some embodiments, scanning system 101 may perform a “fuzzy search” onany usernames found in a password database (e.g., database 103A) todetermine existing targets for password testing. In some embodiments,the fuzzy search uses the Damerau-Levenshtein edit distance algorithm.

As one example, scanning system 101 may determine that a leaked usernameincludes the email address johndoe@acme.com. Scanning system 101 may tryto match passwords from john.doe@acme.net, johndoe@gmail.com, and othervariations. Scanning system 101 may perform a similar process againstleaked passwords (e.g., if a leaked password is “Victory@19,” scanningsystem may attempt to log in using “Victory@20.”

In step 241, scanning system 101 may perform a step of sensitiveinformation scanning. In some embodiments, scanning system 101 maysearch the snapshot for sensitive information, such as personallyidentifiable information (PII), Social Security numbers, healthcareinformation, or credit card numbers. In some embodiments, scanningsystem 101 may search data repository history as well. This is becauseit is not uncommon for an entire production environment repository to becloned, with no one remembering the copy contains sensitive information.In some situations, detecting sensitive data not secured is critical inadherence to data privacy regulations.

To be certain that such alerts do not constitute false positives, insome embodiments, scanning system 101 may perform statistical scansagainst the data. For example, it is possible for a random number toresemble a Social Security number, yet it is extremely unlikely for themajority of a file with thousands of numbers to be valid Social SecurityNumber by pure chance.

In step 243, scanning system 101 may perform a step of containerscanning. In some embodiments, scanning system 101 may apply one or moreof the preceding steps of FIG. 2D against containerized environments. Insome embodiments, in order to do so, scanning system 101 reconstructs acontainer runtime layered file system (LFS) before recursively runningone or more of steps 231-241 on the reconstructed file system.

Scanning system 101 may read network information from the snapshot inorder to determine which services within which containers are exposedexternally and within which ports they are accessible. For example,scanning system 101 may identify a port on which a vulnerableapplication is accessible based on known software vulnerabilities for aversions of software application. Scanning system 101 may query networkaccessibility information via an API provided through a cloud serviceprovider's system and may use it to identify specific vulnerabilitiessusceptible to attack.

After performing step 243 on one or more containers, the process mayreturn to FIG. 2A and step 207 (as discussed above).

Foundational Techniques

Aspects of this disclosure may include establishing a trustedrelationship between a source account in a cloud environment and ascanner account. A trusted relationship, as used herein, may refer to asecure communication channel between at least two accounts (e.g.,domains). The secure communications channel may include, for example, anadministration link, communication link, a connection or communicationnetwork configured with security protocols, or any other securerelationship between two networked entities. A trusted relationshipbetween two accounts may enable user accounts and global groups to beused in a domain other than the domain where the accounts are defined. Asource account, as used herein, may refer to a domain, a location on anetwork server, or anything used to access system resources. A cloudenvironment, as used herein, may refer to a platform implemented on,hosted on, and/or accessing servers that may be reached via the Internetor other shared network. A scanner account, as used herein, may refer toany type of account associated with a scanner. A scanner, as usedherein, may refer to a device for examining, reading, or monitoringelectronically accessible information. FIG. 1 illustrates one example ofa scanner, which is depicted in an exemplary manner as scanning system101.

By way of example, establishing a trusted relationship between a sourceaccount in a cloud environment and a scanner account may include anintegration process (creating a connection between an account onscanning system 101 and an account on cloud infrastructure 106)discussed with reference to FIG. 2A. By way of one example, scanningsystem 101 of FIG. 1 may create a trusted relationship between a sourceaccount in a cloud environment and a scanner account.

Aspects of this disclosure may include using the established trustrelationship, utilizing at least one cloud provider API to identifyworkloads in the source account. A cloud provider API, as used herein,may refer to any application program interface that allows an end userto interact with a cloud providers service. A cloud provider, mayinclude any entity through whom information is accessible over theInternet or other shared network. Workloads, as used herein, may referto systems, devices, or resources in a network (or available via anetwork) such as a cloud infrastructure. By way of example, FIG. 1illustrates examples of a workload: virtual machines 107A-107D,databases 109A-109D, storage 111A-111D, keystores 113A-113D, and loadbalancer 115. In some embodiments, scanning system 101 of FIG. 1 mayperform a scanning operation on workload (e.g., systems, devices,resources, etc.) in cloud infrastructure 106.

In some embodiments, scanning system 101 of FIG. 1 may use an API todetect workloads such as virtual machines 107A-107D, databases109A-109D, storage 111A-111D, keystores 113A-113D, and load balancer 115in the source account.

Aspects of this disclosure may involve using the at least one cloudprovider API to query a geographical location of at least one of theidentified workloads. Querying, as used herein, may refer to a requestfor data or information from a resource. A geographical location, asused herein, may refer to the data center where this workload is served,a position on Earth, a location in a network, an address of a server orother hardware, or any other information capable of identifying a locus,region, or position. Internet geolocation involves software capable ofdeducing a geographic position of a device connected to the Internet.For example, the device's IP address may be used to determine thecountry, city, or ZIP code, determining its geographical location. Byway of example, scanning system 101 of FIG. 1 may query any of workloadsvirtual machines 107A-107D, databases 109A-109D, storage 111A-111D,keystores 113A-113D of cloud infrastructure 106 for their geographicallocation using a cloud provider API.

In some embodiments, the geographic location may include an identifierof a physical site. An identifier, as used herein, may refer to anythingthat allows for recognition of an object, location, or resource. Aphysical site, as used herein, may refer to an actual location. By wayof example, scanning system 101 of FIG. 1 may query any of workloadsvirtual machines 107A-107D, databases 109A-109D, storage 111A-111D,keystores 113A-113D of cloud infrastructure 106 for an identifier oftheir physical site (e.g., address, postal code, or any other physicaldescriptor) using a cloud provider API.

In some embodiments, scanning system 101 of FIG. 1 may use anout-of-band process to reach cloud workloads through a runtime storagelayer, in combination with information gathered from cloud providerAPIs.

Aspects of this disclosure may include receive an identification of thegeographic location. An identification of the geographic location, asused herein, may refer to a recognition, association, or classificationof the geographic location. By way of example, scanning system 101 ofFIG. 1 may receive a geographical location, after querying for it, byinterrogating one or more workloads, such as virtual machines 107A-107D,databases 109A-109D, storage 111A-111D, or keystores 113A-113D of cloudinfrastructure 106. For example, the scanning system 101 of FIG. 1 mayreceive address, postal code, or any other physical descriptor of anyworkloads in cloud infrastructure 106. In some embodiments, scanningsystem 101 of FIG. 1 may receive a listing locating the workloads ofcloud infrastructure 106 on a two-dimensional graphical representation.

In some embodiments, the identification of the geographic location mayinclude an identification of a data center, at least one of a datacenter name, an Internet Protocol (IP) address, a name of the cloudprovider, or a unique identity. A data center, as used herein, may referto a facility that centralizes an organization's shared IT operationsand equipment for the purposes of storing, processing, and/ordisseminating data and applications. A data center, for example, mayinclude a dedicated space within a building, or a group of buildingsused to house computer systems and associated components, such astelecommunications and storage systems. An identification of a datacenter, as used herein, may refer to a recognition, association, orclassification of a data center. A data center name, as used herein, mayrefer to a series of letters or numbers, a word, or set of words ornumbers, an address, or a code identifying the data center. An InternetProtocol (IP) address, as used herein, may refer to a unique string ofcharacters that identifies a computer using the Internet Protocol tocommunicate over a network. A cloud provider, as used herein, may referto a company that offers any components of cloud computing (e.g.,infrastructure as a service (IaaS), software as a service (SaaS) orplatform as a service (PaaS)). A unique identity, as used herein, mayrefer to a distinctive numeric or alphanumeric string that is associatedwith a single entity within a given system.

By way of example, scanning system 101 of FIG. 1 may query for andreceive a geographical location such as a data center name/city andstate, data center address, IP address/specific cloud identifier of theworkload, name of cloud provider (e.g., Amazon Web Services), or aspecific identifier of information of any of workloads such as virtualmachines 107A-107D, databases 109A-109D, storage 111A-111D, keystores113A-113D of cloud infrastructure 106.

In some embodiments, scanning system 101 of FIG. 1 may receive a listingindicating locations of the workloads of cloud infrastructure 106 on atwo-dimensional graphical representation.

In some other embodiments, scanning system 101 may receive additionalinformation (in addition to geographic location information) such aswhether the workload is Internet-facing and easily accessible toattackers, or if it is private (and may be less critical).

Aspects of this disclosure may include using the cloud provider APIs toaccess block storage volumes of the at least one workload. Block storagevolumes, as used herein, may refer to data files maintained on StorageArea Networks (SANs) or in cloud-based storage environments. Eachstorage volume may act as an individual hard drive configured by astorage administrator. Accessing block storage volumes, as used herein,may refer to obtaining, examining, or retrieving data.

As described with relation to process 210 of FIG. 2B (beginning withstep 211 to initiate a connection to cloud infrastructure 106), scanningsystem 101 may send a second message to user device 102, instructing theuser to generate a role. A role may refer to a type associated with anode that may be assigned or defined. The second message may includeinstructions for the user to follow to generate the role. In step 213, auser may provide (e.g., via a keyboard at user device 102) a roledefinition to the cloud service provider's system. In some embodiments,the role definition includes read-only permissions and permissions toread a block storage layer (containing block storage volumes). In someembodiments, scanning system 101 provides a role formation template(e.g., an Amazon Web Services CloudFormation Template) for use withcloud infrastructure 106 to create the necessary role. In step 213, theuser may utilize user device 102, for example, by copying and pasting aURL of the template, downloading and uploading the template to the cloudservice provider's system, or selecting the template from a list oftemplates.

By way of example, scanning system 101 of FIG. 1 may access the blockstorage volume of any of workloads virtual machines 107A-107D, databases109A-109D, storage 111A-111D, keystores 113A-113D of cloudinfrastructure 106.

Aspects of this disclosure may include determining a file-system of theat least one workload. A file-system, as used herein, may refer to amethod and/or a data structure that the operating system uses to controlhow data is stored and retrieved.

By way of example, scanning system 101 of FIG. 1 may identify the typeof file-system of any of workloads virtual machines 107A-107D, databases109A-109D, storage 111A-111D, keystores 113A-113D of cloudinfrastructure 106. Some file systems may include NTFS, FAT32, ext3,exFAT, HFS, HFS+, HPFC, UFS, ZFS.

Aspects of this disclosure may include mounting the block storagevolumes on a scanner based on the determined file-system. Mounting theblock storage volumes, as used herein, may refer to a process by whichthe operating system makes files and directories (such as block storagevolumes) on a storage device available for users to access via thecomputers file system. A scanner, as used herein, may refer to a devicefor examining, reading, or monitoring electronically accessibleinformation. By way of example, FIG. 1 illustrates one example of ascanner, scanning system 101 of FIG. 1. In some embodiments, mountingmay include selecting a driver corresponding to the determined filesystem. In some embodiments, to mount the block storage volumes on thescanner, may include creating a snapshot of the block storage volumes;and mounting the snapshot of the block storage volumes on the scanner. Asnapshot of the block storage volumes, as used herein, may refer to acurrent state or earlier state of the block storage volumes.

In some embodiments, the at least one processor may be furtherconfigured to encrypt the snapshot of the block storage volumes andmount the encrypted snapshot of the block storage volumes on thescanner. Encrypting a snapshot, as used herein, may refer to a processof encoding information (such as a snapshot). This process may convertthe original representation of the information, known as plaintext, intoan alternative form known as ciphertext.

In some embodiments, the scanner may use a privileged account to log inand determine how secure each host is from an inside vantage point.While authenticated scans can successfully discover potentialvulnerabilities, they may be limited to the extent they require aprivileged account on each scanned host. Furthermore, scans usesignificant system resources during the test procedures and requireopening ports that by themselves pose a security risk.

Aspects of this disclosure may include activating a scanner at thegeographic location. Activating a scanner, as used herein, may refer tostarting up or initiating a device for examining, reading, or monitoringdata. By way of example, scanning system 101 of FIG. 1 may start up ascanner (a different scanner than scanning system 101) at the geographiclocation identified by scanning system 101.

Aspects of this disclosure may include reconstructing from the blockstorage volumes a state of the workload. Reconstructing, as used herein,may refer to rebuilding or reforming a state of the workload. A state ofthe workload, as used herein, may refer to a condition of a workload ata certain time. By way of example, scanning system 101 of FIG. 1 mayrebuild the block storage volumes as an earlier version of any ofworkloads such as virtual machines 107A-107D, databases 109A-109D,storage 111A-111D, keystores 113A-113D of cloud infrastructure 106.

In some embodiments, the reconstructed state of the workload may includeat least two of an indication of an installed application, a version ofan installed application, an operating system configuration, anapplication configuration, a profile configuration, a log, or a databasecontent. An indication of an installed application, as used herein, mayrefer to an identifier of a software. A version of an installedapplication, as used herein, may refer to a particular form, variant,edition, or revision of a piece or pieces of software. An operatingsystem configuration, as used herein, may refer to a manner in whichcomponents are arranged to make up an operating system or a computersystem. An application configuration, as used herein, may refer to amanner in which components are arranged to make up an application or acomputer system. A profile configuration, as used herein, may refer to amanner in which components are arranged to make up a profile or acomputer system. A log, as used herein, may refer to a detailed list ofan application information, system performance, or user activities.Database content, as used herein, may refer to any collection of data,or information, that is specially organized for rapid search andretrieval by a computer. In some embodiments, scanning system 101 ofFIG. 1 may reconstruct any workload, such as virtual machines 107A-107D,databases 109A-109D, storage 111A-111D, keystores 113A-113D of cloudinfrastructure 106 from the block storage volumes to an indication of aninstalled application, a version of an installed application, anoperating system configuration, an application configuration, a profileconfiguration, a log, or a database content.

Aspects of this disclosure may include assessing the reconstructed stateof the workload to extract insights. Assessing the reconstructed stateof the workload, as used herein, may refer viewing, utilizing, orevaluating the reconstructed state of the workload. Insights, as usedherein, may refer to information or knowledge attained based on ananalysis of some data. Extracting insights, as used herein, may refer topulling information or data about, for example, a vulnerabilityassociated with the workload or a composition of installed applicationsassociated with the workload. By way of example, scanning system 101 ofFIG. 1 may evaluate the reconstructed state of any of workloads, such asvirtual machines 107A-107D, databases 109A-109D, storage 111A-111D,keystores 113A-113D of cloud infrastructure 106 to pull valuable dataand information.

In some embodiments, insights may include at least one of avulnerability associated with the workload or a composition of installedapplications associated with the workload. A vulnerability, as usedherein, may refer to any weakness within an organization's informationsystems, internal controls, or system processes that can be exploited. Acomposition of installed applications associated with the workload, asused herein, may refer to a structure or group of accessible computerprograms. By way of example, scanning system 101 of FIG. 1 may evaluatethe reconstructed state of any workloads such as virtual machines107A-107D, databases 109A-109D, storage 111A-111D, keystores 113A-113Dof cloud infrastructure 106 to pull valuable data and informationregarding a vulnerability with the workload.

In some embodiments, a scanner may be deployed at the geographicallocation. Deploying a scanner, as used herein, may refer to installing,activating, utilizing, or bringing a scanner into effective action. Byway of example, FIG. 1 illustrates one example of a scanner, scanningsystem 101 of FIG. 1 that is deployed.

In some embodiments, scanning system 101 of FIG. 1 may update thereconstructed state of the workload based on at least one change to theblock storage volumes. Updating the reconstructed state of the workload,as used herein, may refer to overhauling or refurbishing thereconstructed state of the workload. A change to the block storagevolumes, as used herein, may refer to any shift, alteration, ormodification to the block storage volumes.

FIG. 3 illustrates a block diagram of method 300 for insight extraction,consistent with disclosed embodiments. In some embodiments, the methodmay include ten (or more or less) steps:

Block 302: Establish a trusted relationship between a source account ina cloud environment and a scanner account. In some embodiments,establishing a trusted relationship between a source account in a cloudenvironment and a scanner account may include an integration process(creating a connection between an account on scanning system 101 and anaccount on cloud infrastructure 106) discussed with reference to FIG.2A. By way of one example, scanning system 101 of FIG. 1 may create atrusted relationship between a source account in a cloud environment anda scanner account.

Block 304: Using the established trust relationship, utilize at leastone cloud provider API to identify workloads in the source account. Insome embodiments, scanning system 101 of FIG. 1 may use an API to detectworkloads such as virtual machines 107A-107D, databases 109A-109D,storage 111A-111D, keystores 113A-113D, and load balancer 115 in thesource account.

Block 306: Use the at least one cloud provider API to query ageographical location of at least one of the identified workloads. Insome embodiments, scanning system 101 of FIG. 1 may query any ofworkloads virtual machines 107A-107D, databases 109A-109D, storage111A-111D, keystores 113A-113D of cloud infrastructure 106 for theirgeographical location using a cloud provider API.

Block 308: Receive an identification of the geographic location. In someembodiments, scanning system 101 may indicate in the map additionalinformation regarding the workload (e.g., a system or device). Forexample, scanning system 101 may provide: an identification of a datacenter (e.g., a name or number associated with the data center where theworkload is located), at least one of a data center name (e.g., a nameor address associated with the data center where the workload islocated), Internet Protocol (IP) address, name of the cloud provider, ora unique identity (e.g., any other information related to the workloadthat may be used).

Block 310: Use the cloud provider APIs to access block storage volumesof the at least one workload. In some embodiments, scanning system 101of FIG. 1 may access the block storage volume of workloads such asvirtual machines 107A-107D, databases 109A-109D, storage 111A-111D,keystores 113A-113D of cloud infrastructure 106. In some embodiments,accessing the block storage may include taking the mean of generatingsnapshots.

Block 312: Determine a file-system of the at least one workload. In someembodiments, scanning system 101 of FIG. 1 may identify the type offile-system any of workloads (virtual machines 107A-107D, databases109A-109D, storage 111A-111D, keystores 113A-113D of cloudinfrastructure 106).

Block 314: Mount the block storage volumes on a scanner based on thedetermined file-system. In some embodiments, to mount the block storagevolumes on the scanner, may include instructing the operating system tomap a directory structure logically to a physical storage device. Astorage volume may be mounted after it is attached and formatted for useby a server's operating system, Mounting may include creating a snapshotof the block storage.

Block 316: Activate a scanner at the geographic location. In someembodiments, scanning system 101 of FIG. 1 may start up a scanner (adifferent scanner than scanning system 101) at the geographic locationidentified by scanning system 101.

Block 318: Reconstruct from the block storage volumes a state of theworkload. In some embodiments, scanning system 101 of FIG. 1 may rebuildthe block storage volumes to an earlier version of workloads such asvirtual machines 107A-107D, databases 109A-109D, storage 111A-111D,keystores 113A-113D of cloud infrastructure 106.

Block 320: Assess the reconstructed state of the workload to extractinsights. In some embodiments, scanning system 101 of FIG. 1 mayevaluate the reconstructed state of workloads such as virtual machines107A-107D, databases 109A-109D, storage 111A-111D, keystores 113A-113Dof cloud infrastructure 106 to derive valuable data and information.

Vulnerability Management Techniques

FIG. 4 depicts a cybersecurity system performing a side scanningfunction to protect against potential vulnerabilities. Referring to FIG.4, a processor 400 configured to identify in a cloud environment one ormore block storage volumes 401A-C communicatively connected to a cloudprovider API where the block storage volumes 401A-C may be contained.When a block storage volume, e.g., 401A is identified, the processor 400may be configured to perform the function of identifying the softwareinstalled 403A in or relating to block storage volume 401. Uponidentifying installed software 403A, the processor may be furtherconfigured to identify the version of software 405A operating in theinstalled software 403A. Based on the installed software 403A and theversion of the software 405A, the processor may be configured toidentify a listing of known vulnerabilities 407 that may relate to theinstalled software 403A and the version installed 405A. When the listingof known vulnerabilities 407 is obtained, the system may list the knownvulnerabilities 409A for that software version 411A, which can becommunicated to the processor 400 of the end user. This information maybe processed and displayed to an end user using processor 400.

FIG. 5 of the disclosed embodiments describes a method of operating acybersecurity system performing a side scanning function to protectagainst potential vulnerabilities. Referring to FIG. 5, a processor unit500 may be configured to perform the method. When initiated eithermanually or automatically, processor unit 500 may be communicativelyconnected with a cloud provider API 501 to initiate a cybersecurityfunction as disclosed above. Contained digitally on a memory device andaccessed by a cloud provider API 501 is a series of block storagevolumes 503. Processor unit 500 may be capable of performing a verticaland horizontal scan for network access or security information of ablock storage volume 503 to detect potential vulnerabilities to theblock storage volume 503 or any processing unit 500 designed to accesssaid block storage volume 503.

Based on the accessed block storage volume 500, processor unit 500 withthe disclosed embodiments of a cybersecurity system may perform anidentification of the type of software installed 505 connected withblock storage volume 503. Following identification of the type ofsoftware installed 505, the processing unit may then identify aninstalled version 507 of said installed software 505 for a versioncomprised of a unique identifier based on a combination of letters,numbers, or similar unique identifiers.

Upon recognition of an installed software version 507 of the installedsoftware 505, processing unit 500 with the disclosed embodiments of thedisclosed scanning system 101 may provide a list of knownvulnerabilities 509 for review by said scanning system 101 and/or itsend user and maintainer of said block storage volumes 503. Based on thelist of known vulnerabilities 509, the disclosed scanning system 101 orits end user may identify one or more ports of accessibility to saidblock storage volume 503 that may be accessed by a known, associatedvulnerability 513 from listed vulnerabilities 509 to determine an avenuefor potential vulnerability 513 to access and infiltrate block storagevolume 503.

In some embodiments, a cyber security scanning system for a cloudenvironment 101 may include a processor 500 to operate said system. Thisprocessor 500 may include central processing units and other similarcomputer-enabling equipment for processing and executing commands basedon the information inputted to said system. The processor 500 may becommunicatively connected to a computer network or series of networks toaccomplish said cyber security function.

As an example embodiment, a processor unit 500 may be configured to usea cloud-provider API that may communicate with one or more specifiedcomputer-readable media across a digital network. This can beaccomplished through internet protocols, internet control messageprotocols, transmission control protocol, or user datagram protocol.Cloud provider API 501 may be one of several forms of middleware,interface, middle layer, or other systems of interfacing applications. Aprocessor 300 may be one or more computer processing units, centralprocessing unit, server, microcomputer, mainframe, and any othermanifestation of digital computing.

Further to one of several possible embodiments, a cloud-provider API 501may be configured to access a block-storage volume 503 of a workloadmaintained in a cloud-storage environment. This may be accomplishedthrough a system of computer-readable media communicatively connected.Said block-storage volume 303 may be contained on a Storage Area Network(SAN) or similar cloud-based memory storage environment. The blockstorage volume 503 may be contained in smaller storage volumes with anassociated identifier unique to that portion of said block storagevolume 503. In some embodiments, the block-storage volume 503 of aworkload may have multiple paths for the storage volume to bereaggregated and retrieved quickly.

Among several embodiments, a scanning system 101 may comprise a systemfor identifying an installed software application in the accessedblock-storage volume 503. This identification of installed software maybe accomplished by accessing installed software 505 files throughsignature verification, root license, or authorized user lists. Theinstalled software 505 may be located and identified within applicationssuch as file storage, database storage, and virtual machine file systemvolumes. The identification of said installed software application 507may be processed, analyzed, and communicated to the scanning system 101for processing, cataloging, and protection through encryption andvarious methods of layered cyber defense.

Further, the scanning system 101 described herein may includefunctionality to analyze installed software applications to determinethe associated software version. The software application version 507may identify the software version based on unique version name, uniqueversion number, and may be based on unique states of the currentlyinstalled computer software 505.

One of many embodiments disclosed above may include the scanning system101 having the ability to access a data structure of known softwarevulnerabilities 509 for a plurality of versions of softwareapplications. The known software vulnerabilities 509 may include, amongothers, missing data encryption, OS command injection, SQL injection,buffer overflow, missing authentication, missing authorization,unrestricted upload of dangerous file types, reliance on untrustedinputs in a security decision, cross-site scripting and forgery,download of codes without integrity checks, broken algorithms, URLredirection, path traversal, software bugs, weak passwords, andpreviously infected software. The scanning system 101 may be able toaccess and identify software vulnerabilities for mitigation,rectification, correction, and fortification.

In one embodiment, a cybersecurity system may also perform scanningaccording to scanning system 101 by performing a lookup of theidentified installed software version 507 in the data structure toidentify known vulnerabilities 509. This function can be performed bythe scanning system 101 according to FIG. 1 performing a query of theinstalled software 505 for unique version number or designator andcomparing to, amongst many things, a set of likely or potentialvulnerabilities to that software version for potential deficiencies orcybersecurity threats known or suspected to similar software types andversions. This query may be performed according to a predetermined setof values, to include previously identified unique version numbers ordesignators that may contain the known list of previously identifiedvulnerabilities.

Among many embodiments, embodiments of the disclosed scanning system 101may query the cloud provider API 501 to determine network accessibilityinformation 511 related to the workload. In order to accomplish thisquery of the cloud provider API 301, the scanning system 101 may involveindex of search results and display of said search results, followed byprocessing and grouping search results. Network accessibilityinformation 511 may include connection quality, alternative pathsbetween nodes in a network, and the ability to avoid blockage in saidnetworks. The workloads associated with this query may includeapplications, services, capabilities, and specific processes such asvirtual machines, databases, containers, or Hadoop nodes, among others.

If the system detects a vulnerable application 513, one embodiment mayidentify one or more port on which said vulnerable application isaccessible. In one of several embodiments, the scanning system 101 maydetect a vulnerable application in one or more computation process. Inanother embodiment, the cybersecurity system may perform a networkaccessibility query in a separate process. Further, a disclosedembodiment may perform these separate functions in subsequent andsequential steps of the same process. A person having skill wouldunderstand that an authorized user or an authorized scanning system 101can perform these functions concurrently and subsequently by anauthorized user or an authorized cybersecurity system while performingthe same function as the disclosed embodiment.

Upon gathering network accessibility information and the identified portto identify one or more vulnerabilities susceptible to attack fromoutside the workload, a disclosed embodiment would have thefunctionality to perform processes to gather, display, and mitigate adiscovered vulnerability in order to minimize the likelihood andeffectiveness of a cyber threat outside of and attempting to access aworkload through a known or previously encountered type of cyber threat.This functionality may include collecting and organizing thevulnerabilities according to type or category of vulnerability,displaying the gathered data for an end user or maintainer, andimplementing security features automatically or manually by a user ormaintainer such as security patches, password or passcode changes andsuggestions for users to do the same, and malicious code eradication.

As one of several possible embodiments, the scanning system 101 mayalso, upon identification of one or more vulnerabilities, implementremedial actions via one or more processors. Remedial actions mayinclude, among other things, notification to an end user of anidentified threat, compensation through a revised security code tomitigate the potential threat, publication of the identified threat andvulnerability in a log or record of detected vulnerabilities, andcommunication of the sensed vulnerability and threat to a serveroperator or maintainer to fortify the protections of workloads existingon similar environments.

In a similar embodiment to above, the remedial measure may includetransmission of an alert to a device associated with an administrator.The alert may be, amongst others, written, auditory, and visual forprocessing and use by an administrator of said scanning system 101. Saidadministrator may take action based on the received alert, to includeeliminating the cyber threat through mitigation measures, change incybersecurity posture, or removing the workload from the cybersecuritythreat environment.

In another embodiment, a query of the cloud provider API 501 todetermine network accessibility information related to the workload maybe performed by at least one processor 500 configured to examine datasources associated with the workload. The data examined may include userdata, system processing data, accessibility data, clock cycles, storageinput/output, or similar data processors. A query of the cloud providerAPI 501 may be automated or manually-initiated. Based on the said query,the network accessibility information 511 related to the workload maychange based on the data sources associated with said workload.

In the above processor and similar embodiments, further configurationmay include a process to determine network accessibility information 511based on the examined data sources. The examined data sources mayinclude various cloud-based workloads, internet protocols, transmissioncommunication protocols, or other methods and systems of memory and datastorage.

As an exemplary embodiment, network accessibility information 511includes at least one of: data from an external data source, cloudprovider information, or at least one network capture log. Theseembodiments of an external data source may include data from theoperating environment of the cloud-based environment, an externaloperating system for a computer processing unit 500, or other similarcomputer readable media. Cloud provider information may further includeinformation that may identify the network accessibility information 511vertically or horizontally to fully describe the associated workload.Network capture logs may be automated or manually updated to includepossible vulnerabilities 513 and threats to the cloud-based storagemedium.

Further, the disclosed embodiments may include an installed softwareapplication 505, with the at least one processor 500 configured toextract data from at least one of operating system packages, libraries,or program language libraries. This data may be extracted through asystem query, random access algorithm, or similar automated process.Operating system packages may include systems operable on Microsoft,Apple, Linux, and similar operating systems. Libraries may consist of aseries of files, folders, and databases of information stored on one ofany indexed data repositories. A program language library may containseveral of an exemplary program languages including but not limited toJavascript, Swift, Scala, Go, Python, Elm, Ruby, C#, C++ and othersimilar sources of software code.

As another exemplary embodiment, a scanning system 101 may also includea processor 500 configured to identify installed software application505 based on the extracted data. The processor 500 may perform only thisfunction or this function among many to accomplish the layeredcybersecurity defense described herein this disclosed cloud-basedsecurity environment. The identification of installed software by saidprocessor may include identifying the software by unique version numberor designator, recognized source code, metadata associated with theinstalled software application files, or similar software-identifyinginformation.

One embodiment may include an additional function wherein the installedsoftware application 505 that has been identified includes one or morescripts. These scripts may be processed through various computerreadable languages to include Javascript, C#, C++ and other forms ofcomputer code.

One embodiment contemplated by the disclosed scanning system 101 mayalso include data structure includes aggregated vulnerability data 309.This aggregated vulnerability data 509 may be compiled by an end user ormaintainer from within the cloud-based environment of the current datastructure as well as compilation from similar data sets and aggregationof common threats to data structures likely to experience similarvulnerabilities. This aggregation of vulnerability data 509 may becontained within the data structure and it may be collectivelyaggregated to provide for a more robust and layered cybersecuritydefense posture.

In an embodiment of the disclosed scanning system 101, the aggregatedvulnerability data 509 may include data from one or more third-partyvendors. These vendors may include operators of the cloud-based serverenvironment, providers of networking and internet communication, methodsof layered authentication, and other similar providers of servicesdirectly related and in communication with the cloud-based cybersecuritysystem.

As an additional exemplary embodiment, the aggregated vulnerability data309 may include data collected by a scanner. This scanner may involveuse of continuous or periodic monitoring of the workload. The scannermay perform security screenings of the various workloads vertically orhorizontally to identify network identification information, portaccessibility, and associated vulnerabilities. Any scan performed may becommunicated to the scanning system 101 that may be responsible forperforming and logging the results of the scan and may be able toinitiate follow-on processes and protocols to protect the data containedin the workload that is the subject of scanning.

An embodiment of the disclosed scanning system 101 may also includeaggregated vulnerability data 509 that may include at least one of anadvisory, an exploit, a security announcement, or a known bug. Anadvisory may include notification to a system maintainer or user of thepotential vulnerability, may log notice of the advisory, and mayrecommend possible user or maintainer actions to potentially addresssaid advisory. An exploit may further consist of an automated systemresponse designed to take advantage of the sensed vulnerability data.The exploit can be further reflected in the aggregated vulnerabilitydata and protocols can be written into the cybersecurity infrastructureto prevent said exploit from gaining access and permissions tounauthorized areas of the workload storage environment.

A person having ordinary skill in the art would appreciate the abovedescribed embodiments are among many potential embodiments, to include amethod of operating a scanning system 101 similar to the one describedabove. A disclosed embodiment contemplates this method to beaccomplished through manual user operation, automated computerprocesses, or similar manners of operation. These manners of operationand those contemplated similar to them would allow the scanning system101 described and disclosed to execute its operations as the systemabove describes.

One of several embodiments of the disclosed method of operating ascanning system 101 may include a cyber security scanning system for acloud environment 101 may include a processor 500 to operate saidsystem. This processor may include central processing units and othersimilar computer-enabling equipment for processing and executingcommands based on the information inputted to said system. The processormay be communicatively connected to a computer network or series ofnetworks to accomplish said cyber security function.

As an example embodiment, a processor unit 500 may be configured to usea cloud-provider API 501 that may communicate with one or more specifiedcomputer-readable media across a digital network. This can beaccomplished through internet protocols, internet control messageprotocols, transmission control protocol, or user datagram protocol.Cloud provider API 501 may be one of several forms of middleware,interface, middle layer, or other systems of interfacing applications. Aprocessor may be one or more computer processing units, centralprocessing unit, server, microcomputer, mainframe, and any othermanifestation of digital computing.

Further to one of several possible embodiments, a cloud-provider API 501may be configured to access a block-storage volume 503 of a workloadmaintained in a cloud-storage environment. This may be accomplishedthrough a system of computer-readable media communicatively connected.Said block-storage volume 503 may be contained on a Storage Area Network(SAN) or similar cloud-based memory storage environment. The blockstorage volume 503 may be contained in smaller storage volumes with anassociated identifier unique to that portion of said block storagevolume 503. In some embodiments, the block-storage volume 503 of aworkload may have multiple paths for the storage volume to bereaggregated and retrieved quickly.

Among several embodiments, a method of operating a scanning system 101may comprise a system for identifying an installed software application505 in the accessed block-storage volume 503. This identification ofinstalled software 505 may be accomplished by accessing installedsoftware files through signature verification, root license, orauthorized user lists. The installed software 505 may be located andidentified within applications such as file storage, database storage,and virtual machine file system volumes. The identification of saidinstalled software application 505 may be processed, analyzed, andcommunicated to the method of operating a scanning system 101 forprocessing, cataloging, and protection through encryption and variousmethods of layered cyber defense.

Further, a method of operating a scanning system 101 described hereinmay include functionality to analyze installed software applications 505to determine the associated software version 507. The softwareapplication version 507 may identify the software version based onunique version name, unique version number, and may be based on uniquestates of the currently installed computer software.

One of many embodiments disclosed above may include the method ofoperating a scanning system 101 having the ability to access a datastructure of known software vulnerabilities 509 for a plurality ofversions of software applications 507. The known softwarevulnerabilities 509 may include, among others, missing data encryption,OS command injection, SQL injection, buffer overflow, missingauthentication, missing authorization, unrestricted upload of dangerousfile types, reliance on untrusted inputs in a security decision,cross-site scripting and forgery, download of codes without integritychecks, broken algorithms, URL redirection, path traversal, softwarebugs, weak passwords, and previously infected software. The cybersecurity system may be able to access and identify softwarevulnerabilities 309 for mitigation, rectification, correction, andfortification.

In one embodiment, a method of operating a scanning system 101 may alsoperform scanning according to scanning system 101 by performing a lookupof the identified installed software version 507 in the data structureto identify known vulnerabilities 309. This function can be performed bythe scanning system 101 according to FIG. 1 performing a query of theinstalled software 505 for unique version number 507 or designator andcomparing to, amongst many things, a set of likely or potentialvulnerabilities to that software version for potential deficiencies orcybersecurity threats known or suspected to similar software types andversions. This query may be performed according to a predetermined setof values, to include previously identified unique version numbers ordesignators that may contain the known list of previously identifiedvulnerabilities.

Among many embodiments, embodiments of the disclosed method of operatinga scanning system 101 may query the cloud provider API 501 to determinenetwork accessibility information 511 related to the workload. In orderto accomplish this query of the cloud provider API 501, the scanningsystem 101 may involve index of search results and display of saidsearch results, followed by processing and grouping search results.Network accessibility information 511 may include connection quality,alternative paths between nodes in a network, and the ability to avoidblockage in said networks. The workloads associated with this query mayinclude applications, services, capabilities, and specific processessuch as virtual machines, databases, containers, or Hadoop nodes, amongothers.

If the system detects a vulnerable application, one embodiment mayidentify one or more port on which said vulnerable application isaccessible. In one of several embodiments, the scanning system 101 maydetect a vulnerable application in one or more computation process. Inanother embodiment, the scanning system 101 may perform a networkaccessibility query in a separate process. Further, a disclosedembodiment may perform these separate functions in subsequent andsequential steps of the same process. A person having skill wouldunderstand that an authorized user or an authorized cybersecurity systemmay perform these functions concurrently and subsequently whileperforming the same function as the disclosed embodiment.

Upon gathering network accessibility information 511 and the identifiedport 513 to identify one or more vulnerabilities susceptible to attackfrom outside the workload, a disclosed embodiment would have thefunctionality to perform processes to gather, display, and mitigate adiscovered vulnerability in order to minimize the likelihood andeffectiveness of a cyber threat outside of and attempting to access aworkload through a known or previously encountered type of cyber threat.This functionality may include collecting and organizing thevulnerabilities according to type or category of vulnerability,displaying the gathered data for an end user or maintainer, andimplementing security features automatically or manually by a user ormaintainer such as security patches, password or passcode changes andsuggestions for users to do the same, and malicious code eradication.

A person having ordinary skill in the art would similarly understandthat the above disclosed system can be disclosed using a suitablenon-transitory computer-readable medium performing each of the disclosedfunctions. The disclosed embodiment may include a non-transitorycomputer readable medium with a scanning system 101 similar to the onedescribed above on a non-transitory computer-readable medium. Adisclosed embodiment contemplates this system to be accomplished througha medium that may contain a central processing unit, virtual machine, ora similar non-transitory medium. These manners of operation and thosecontemplated similar to them would allow the scanning system 101described and disclosed to execute its operations as the system abovedescribes.

One of several embodiments of the disclosed non-transitory computerreadable medium with a scanning system 101 may include a cyber securityscanning system for a cloud environment 101 may include a processor 500to operate said system. This processor 500 may include centralprocessing units and other similar computer-enabling equipment forprocessing and executing commands based on the information inputted tosaid system. The processor 500 may be communicatively connected to acomputer network or series of networks to accomplish said cyber securityfunction.

As an example embodiment, a processor unit 300 may be configured to usea cloud-provider API 501 that may communicate with one or more specifiedcomputer-readable media across a digital network. This can beaccomplished through internet protocols, internet control messageprotocols, transmission control protocol, or user datagram protocol.Cloud provider API 501 may be one of several forms of middleware,interface, middle layer, or other systems of interfacing applications. Aprocessor 500 may be one or more computer processing units, centralprocessing unit, server, microcomputer, mainframe, and any othermanifestation of digital computing.

Further to one of several possible embodiments, a cloud-provider API 501may be configured to access a block-storage volume 503 of a workloadmaintained in a cloud-storage environment. This may be accomplishedthrough a system of computer-readable media communicatively connected.Said block-storage volume 503 may be contained on a Storage Area Network(SAN) or similar cloud-based memory storage environment. The blockstorage volume 503 may be contained in smaller storage volumes with anassociated identifier unique to that portion of said block storagevolume 503. In some embodiments, the block-storage volume 503 of aworkload may have multiple paths for the storage volume to bereaggregated and retrieved quickly.

Among several embodiments, a non-transitory computer readable mediumwith a scanning system 101 may comprise a system for identifying aninstalled software application 505 in the accessed block-storage volume503. This identification of installed software 505 may be accomplishedby accessing installed software files through signature verification,root license, or authorized user lists. The installed software 505 maybe located and identified within applications such as file storage,database storage, and virtual machine file system volumes. Theidentification of said installed software application 505 may beprocessed, analyzed, and communicated to the method of operating ascanning system 101 for processing, cataloging, and protection throughencryption and various methods of layered cyber defense.

Further, a non-transitory computer readable medium with a scanningsystem 101 described herein may include functionality to analyzeinstalled software applications 505 to determine the associated softwareversion 507. The software application version 507 may identify thesoftware version based on unique version name, unique version number,and may be based on unique states of the currently installed computersoftware.

One of many embodiments disclosed above may include the non-transitorycomputer readable medium with a scanning system 101 having the abilityto access a data structure of known software vulnerabilities 509 for aplurality of versions of software applications 507. The known softwarevulnerabilities 509 may include, among others, missing data encryption,OS command injection, SQL injection, buffer overflow, missingauthentication, missing authorization, unrestricted upload of dangerousfile types, reliance on untrusted inputs in a security decision,cross-site scripting and forgery, download of codes without integritychecks, broken algorithms, URL redirection, path traversal, softwarebugs, weak passwords, and previously infected software. The scanningsystem 101 may be able to access and identify software vulnerabilitiesfor mitigation, rectification, correction, and fortification.

In one embodiment, a non-transitory computer readable medium with ascanning system 101 may also perform scanning according to scanningsystem 101 by performing a lookup of the identified installed softwareversion in the data structure to identify known vulnerabilities 509.This function can be performed by the scanning system 101 according toFIG. 1 performing a query of the installed software for unique versionnumber 307 or designator and comparing to, amongst many things, a set oflikely or potential vulnerabilities 309 to that software version 307 forpotential deficiencies or cybersecurity threats known or suspected tosimilar software types and versions. This query may be performedaccording to a predetermined set of values, to include previouslyidentified unique version numbers or designators that may contain theknown list of previously identified vulnerabilities 509.

Among many embodiments, embodiments of the disclosed non-transitorycomputer readable medium with a scanning system 101 may query the cloudprovider API 501 to determine network accessibility information 511related to the workload. In order to accomplish this query of the cloudprovider API 501, the scanning system 101 may involve index of searchresults and display of said search results, followed by processing andgrouping search results. Network accessibility information 511 mayinclude connection quality, alternative paths between nodes in anetwork, and the ability to avoid blockage in said networks. Theworkloads associated with this query may include applications, services,capabilities, and specific processes such as virtual machines,databases, containers, or Hadoop nodes, among others.

If the system detects a vulnerable application, one embodiment mayidentify one or more ports 515 on which said vulnerable application isaccessible. In one of several embodiments, the scanning system 101 maydetect a vulnerable application in one or more computation processes. Inanother embodiment, the scanning system 101 may perform a networkaccessibility query in a separate process. Further, a disclosedembodiment may perform these separate functions in subsequent andsequential steps of the same process. A person having skill wouldunderstand that an authorized user or an authorized cybersecurity systemcan perform these functions concurrently and subsequently whileperforming the same function as the disclosed embodiment.

Upon gathering network accessibility information 511 and the identifiedport 515 to identify one or more vulnerabilities susceptible to attackfrom outside the workload, a disclosed embodiment would have thefunctionality to perform processes to gather, display, and mitigate adiscovered vulnerability in order to minimize the likelihood andeffectiveness of a cyber threat outside of and attempting to access aworkload through a known or previously encountered type of cyber threat.This functionality may include collecting and organizing thevulnerabilities according to type or category of vulnerability,displaying the gathered data for an end user or maintainer, andimplementing security features automatically or manually by a user ormaintainer such as security patches, password or passcode changes andsuggestions for users to do the same, and malicious code eradication.

Another disclosed embodiment may include a method of using a cloudprovider API 501, accessing block storage volume 503 of a workloadmaintained in a cloud storage environment. The method may include manualuser operation, automated system operation, systematic and randomoperating parameters for the system to provide its cybersecurity andsimilar security functions. The accessed block storage volume may becontained as a collection of block units organized together, may be aseries of individual blocks that can be reorganized to form a newstorage volume, and may have the ability to be disaggregated andreaggregated as necessary to accomplish its storage and cybersecurityfunctions.

The disclosed method may further comprise a system that may analyze theidentified installed software application 505 to determine an associatedsoftware version 507. In analyzing an installed software application305, the disclosed embodiment may include a method of querying theinstalled software application to access a software version 507 that mayinclude a series of letters, numbers, and other identifying charactersto differentiate the version of software currently operative and itsassociated identifying characteristics and capabilities.

A method of the disclosed may also include accessing a data structure ofknown software vulnerabilities 509 for a plurality of versions ofsoftware applications 507. The disclosed method may determine a datastructure of known software vulnerabilities 509 of one among manyoperative versions of software installed in the monitored storage systemas compared to historical data of similar storage systems.

The disclosed method as described herein may further include performinga lookup of the identified installed software version 507 in the datastructure to identify known vulnerabilities 509. The lookup ofidentified installed software 507 may be previously indexed based onunique version identifier, and the indexed information may include knownvulnerability information 509, network accessibility information 511,network protocols, and administrator identifier information. Based onthe said indexed known vulnerabilities 509, the scanning system 101disclosed may take actions to mitigate a cybersecurity threat andreinforce cybersecurity defenses at the type of cybersecurity threat, aspreviously discussed.

Further to the above, a disclosed method may also include querying thecloud provider API 501 to determine network accessibility information511 related to the workload. A query of the cloud provider API 501 todetermine network accessibility information 511 related to the workloadmay be automatically or manually initiated. Network accessibilityinformation 511 similar to the above embodiment may include connectionquality, alternative paths between nodes in a network, and the abilityto avoid blockage in said networks. The workloads associated with thisquery may include applications, services, capabilities, and specificprocesses such as virtual machines, databases, containers, and Hadoopnodes, among others.

A disclosed method of one embodiment also may provide a method ofidentifying at least one port 515 on which the vulnerable application isaccessible. The identification of one port 515 on which the vulnerableapplication is accessible may be for the purpose of identifying a cyberweakness, and it may include the ability to change the port currentlyaccessible to mitigate the said cyber weakness.

Yet another disclosed embodiment of a disclosed method may include usingthe network accessibility information 511 and the identified at leastone port 515 to identify one or more vulnerabilities 513 susceptible toattack from outside the workload. The vulnerability 513 identified assusceptible to attack from outside the workload may include, amongothers, missing data encryption, OS command injection, SQL injection,buffer overflow, missing authentication, missing authorization,unrestricted upload of dangerous file types, reliance on untrustedinputs in a security decision, cross-site scripting and forgery,download of codes without integrity checks, broken algorithms, URLredirection, path traversal, software bugs, weak passwords, andpreviously infected software.

A method of the disclosed embodiment may further include implementing aremedial action in response to the identified one or morevulnerabilities 513. Said remedial action may include, among otherthings, notification to an end user of an identified threat,compensation through a cybersecurity patch, publish of the identifiedthreat and vulnerability in a log or record of detected vulnerabilities,and communication of the sensed vulnerability and threat to a serveroperator and maintainer to fortify the protections of workloads existingon similar environments.

The disclosed method may also include wherein the remedial measureincludes transmitting an alert to a device associated with anadministrator. Said alert may be, amongst others, written, auditory, andvisual for processing and use by an administrator of said cybersecuritysystem. Said alert may further be logged and catalogued for futureidentification of known threats and vulnerabilities to similar softwareapplication versions.

A disclosed method of the present embodiment may also provide queryingthe cloud provider API 501 to determine the network accessibilityinformation 311 related to the workload and examining data sourcesassociated with the workload. A query of the cloud provider API 501 todetermine network accessibility information 511 related to the workloadmay be automatically or manually initiated. Network accessibilityinformation 511 similar to the above embodiment may include connectionquality, alternative paths between nodes in a network, and the abilityto avoid blockage in said networks. The workloads associated with thisquery may include applications, services, capabilities, and specificprocesses such as virtual machines, databases, containers, and Hadoopnodes, among others.

The method of the above disclosed embodiment may further determinenetwork accessibility information 511 by determining the networkaccessibility information 511 based on the examined data sources. Thedata examined may include user data, system processing data,accessibility data, clock cycles, storage input/output, and similarprocesses. A query of the cloud provider API 501 may be automated ormanually-initiated. Based on the said query, the network accessibilityinformation 511 related to the workload may change based on the datasources associated with said workload.

In the method of one disclosed embodiment, network accessibilityinformation 511 may include at least one of data from an external datasource, cloud provider information, or at least one network capture log.These embodiments may include data from the operating environment of thecloud-based environment, an external operating system for a computerprocessing unit, or other similar computer readable media. Networkcapture logs may be automated or manually updated to include possiblevulnerabilities and threats to the cloud-based storage medium.

A method of the disclosed embodiment may also include identifying theinstalled software application 507 by extracting data from at least oneof OS packages, libraries, or program language libraries. This data maybe extracted through a system query, random access algorithm, or similarautomated process. Operating system packages may include systemsoperable on Microsoft, Apple, Linux, and similar operating systems.Libraries may consist of a series of files, folders, and databases ofinformation stored on one of any indexed data repositories. A programlanguage library may contain several of an exemplary program languagesincluding but not limited to Javascript, Swift, Scala, Go, Python, Elm,Ruby, C#, C++ and other similar sources of software code.

Another method of the disclosed embodiment may identify the installedsoftware application 507 based on the extracted data. The method of theprocessor 500 may perform only this function or this function among manyto accomplish the layered cybersecurity defense described herein thisdisclosed cloud-based security environment.

A further disclosed method of the present embodiment may include atleast one processor 500 further configured to identify a version 507 ofthe installed software application 505. The method of the processor mayperform only this function or this function among many to accomplish thelayered cybersecurity defense described herein this disclosedcloud-based security environment.

Prioritization Techniques

FIG. 6 is a block diagram of method 600 for risk prioritization,consistent with disclosed embodiments.

Aspects of this disclosure may include a cloud-based cybersecuritysystem for assessing internet exposure of a cloud-based workload withembodiments configured to access at least one cloud provider API todetermine a plurality of entities capable of routing and/or filteringtraffic in a virtual cloud environment associated with a target accountcontaining the workload. Routing traffic, as used herein, may refer tothe process of selecting a path for traffic (e.g., cells, blocks,frames, packets, calls, messages, or other units of data) in a networkor between or across multiple networks. The cloud-based cybersecuritysystem, in some embodiments, may comprise at least one processorconfigured to assess internet exposure as described herein.

A cloud provider API, as used herein, may refer to any applicationprogram interface that allows the end user to interact with a cloudproviders service. Workloads, as used herein, may refer to devices in anetwork. By way of example, workloads may include systems, devices,resources in a cloud infrastructure. By way of example, FIG. 1illustrates examples of a workload, such as virtual machines 107A-107D,databases 109A-109D, storage 111A-111D, keystores 113A-113D, or loadbalancer 115. In some embodiments, scanning system 101 of FIG. 1 mayperform a scanning operation on any workload (e.g., systems, devices,resources, etc.) in cloud infrastructure 106.

In some embodiments, scanning system 101 of FIG. 1 may use an API todetect workloads such as virtual machines 107A-107D, databases109A-109D, storage 111A-111D, keystores 113A-113D, and load balancer 115in the source account. In some embodiments, workloads may exist asvirtual machines, while in other embodiments, workloads may exist asdiscrete, physical devices. For example, in some embodiments, a layer 3routing system could be implemented as a physical device (e.g., a routeror switch) or a virtual device (e.g., a routing system instantiated as avirtual device on a computer).

Scanning system 101 may query devices and systems capable of routing andfiltering traffic (e.g., load balancer 115, routers, switches,firewalls, security groups, API Gateways and proxies) using an APIprovided through a cloud service provider's system to determine networkconfigurations, and may evaluate them against known problematicconfigurations or other configurations. These devices can be cloudnative and/or unmanaged (e.g. NGINX proxy)

A cloud environment, as used herein, may refer to a platform implementedon, hosted on, and/or accessing servers that are accessed over theInternet. A scanner account, as used herein, may refer to any type ofaccount associated with a scanner. A scanner, as used herein, may referto a device for examining, reading, or monitoring something. By way ofexample, FIG. 1 illustrates one example of a scanner, scanning system101 of FIG. 1. A target account containing the workload, as used herein,may refer to a location on a network server selected as an aim ofconnection, for example. In some embodiments, scanning system 101 ofFIG. 1 may determine entities capable of routing traffic.

In some embodiments, the plurality of entities includes a virtualnetwork appliance. A virtual network appliance, as used herein, mayrefer to a machine focused on virtualizing network functionality. Insome embodiments, a typical network virtual appliance may includefunctionality directed to various layer four to seven. That is, suchappliances may implement functionality associated with OSI model layers4-7 (Transport, Session, Presentation, and Application). Suchfunctionality may include, for example, a firewall, WAN optimizer,application delivery controllers, routers, load balancers, IDS/IPS,proxies, or SD-WAN edge device. In some embodiments, scanning system 101of FIG. 1 may determine a virtual network appliance capable of routingtraffic.

In some embodiments, the virtual network appliance is at least one of aload balancer, a firewall, a proxy, or a router. A load balancer, asused herein, may refer to any device that acts as a reverse proxy anddistributes network or application traffic across a number of servers.In some embodiments, load balancer 115 may comprise one or more systemsthat balance incoming requests between the different systems and devicesof cloud infrastructure 106. For example, load balancer 115 may beconfigured to determine usage (e.g., processor load, used storagecapacity) of systems or devices in cloud infrastructure 106 to assist indetermining where to route an incoming request from network 105 to storedata, perform processing, or retrieve data.

Load balancer 115 may be configured to receive an incoming request fromuser device 102. Upon receipt of the request, load balancer 115 mayconsult a data store (part of or separate from load balancer 115; notpictured) to determine usage or forecasted usage of various systems ordevices in cloud infrastructure 106, and may forward the request to thesystems or devices having the lowest usage or forecasted usage. Afirewall, as used herein, may refer to a device or system that monitorsincoming and outgoing network traffic and permits or blocks data packetsbased on a set of security rules. A proxy, as used herein, may refer toa device or system that translates traffic between networks orprotocols. In some embodiments, a proxy may be implemented as anintermediary a device or system separating end-user devices fromdestinations devices (e.g., web servers) by routing traffic throughthem. Proxies (or proxy servers) may be configured to provide varyinglevels of functionality, security, and privacy depending on use case,needs, or company policy. A router, as used herein, may refer to adevice or system that connects a local network to the internet.

Aspects of this disclosure may include embodiments in which acloud-based cybersecurity system is configured to query the at least onecloud provider API to determine at least one networking configuration ofthe entities. Querying, as used herein, may refer to a request for dataor information from a resource. A cloud provider API, as used herein,may refer to any application program interface that allows an end userto interact with a cloud providers service. A cloud provider may includeany entity through whom information is accessible over the Internet orother shared network. At least one networking configuration of theentities, as used herein, may refer to a manner in which components arearranged to make up an operating system, networking system, or acomputer system. In some embodiments, scanning system 101 of FIG. 1 maysend a request to determine at least one networking configuration of theentities.

In some embodiments, the networking configuration is at least one of arouting configuration, a proxy configuration, a load balancingconfiguration, a firewall configuration, or a VPN configuration.

A routing configuration, as used herein, may refer to a manner in whichcomponents are arranged to make up a routing system. For example, arouting configuration may provide for dynamic or static “routes” betweendevices on a network or on networks.

A proxy configuration, as used herein, may refer to a manner in whichcomponents are arranged to make up a proxy system. For example, a proxyconfiguration may provide for a configuration of how a client can routetraffic through a central point (e.g., a proxy server), in order torelay multiple clients' requests from a single point on a network.

A load balancing configuration, as used herein, may refer to a manner inwhich components are arranged to make up a load balancing system. Forexample, a loan balancing configuration may define how resources such asuplinks or distributed applications may be utilized by devices on thesame (or another) network, in order to balance usage of multipleredundant uplinks or distributed application nodes.

A firewall configuration, as used herein, may refer to a manner in whichcomponents are arranged to make up a firewall system. For example, afirewall configuration may comprise rules that determine what trafficmay be forwarded, which devices are permitted to communicate with oneanother, or what protocols may be used for communication betweendevices.

A VPN (virtual private network) configuration, as used herein, may referto a manner in which components are arranged to make up a VPN system. AVPN may refer to a type of network that extends a private network acrossa public network and enables users to send and receive data acrossshared or public networks as if their computing devices were directlyconnected to the private network. For example, a VPN configuration mayprovide rules or other information by which data is sent or receivedover a single, encrypted route, such that intermediate points cannotdetermine the content, source, or destination of the data.

In some embodiments, scanning system 101 of FIG. 1 may send a request todetermine at least a routing configuration, a proxy configuration, aload balancing configuration, a firewall configuration, or a VPNconfiguration of the entities.

Aspects of this disclosure may include embodiments in which acloud-based cybersecurity system is configured to build a graphconnecting the plurality of entities based on the networkingconfiguration. A graph connecting the plurality of entities, as usedherein, may refer to a diagram showing the relation between variablequantities (e.g., entities). In some embodiments, the graph may includeany data structures that includes the connections from one entity toanother. In some embodiments, scanning system 101 of FIG. 1 mayconstruct a graph or diagram linking the plurality of entities based onthe networking configuration. In some embodiments, graph includes a datastructure sequentially connecting entities. A data structuresequentially connecting entities, as used herein, may refer to anorganization, management, and/or storage format that enables efficientaccess and modification of data such as entities.

In some embodiments, a graph may include directional vectors indicatingdirections of dataflow. Directional vectors, as used herein, may referto a quantity having direction as well as magnitude (indicating, forexample, what kinds of traffic are allowed to flow, what ports are open,what protocols are allowed), especially as determining the position ofone point in space relative to another. Directions of dataflow, as usedherein, may refer to the movement of data through a system comprised ofsoftware, hardware or a combination of both along a particular course.In some embodiments, scanning system 101 of FIG. 1 may construct a graphincluding a data structure connecting entities sequentially or a graphincluding directional vectors showing the direction of data flow.

In some embodiments, to build the graph, the at least one processor maybe configured to identify individual entities as nodes and connect thenodes. Nodes, as used herein, may refer to a device in a network (e.g.,devices in cloud infrastructure 100). Connecting nodes, as used herein,may refer to linking or bonding devices or data points in a largernetwork. In some embodiments, the graph includes port numbers associatedwith the workload. Port numbers, as used herein, may refer to a way toidentify a specific process to which an internet or other networkmessage is to be forwarded when it arrives at a server and/or whichservices are running on a server. In some embodiments, the graphincludes a path from the at least one source to the workload. A pathfrom the at least one source to the workload, as used herein, may referto a string of characters used to uniquely identify a location in adirectory structure.

Aspects of this disclosure may include embodiments in which acloud-based cybersecurity system is configured to access a datastructure identifying services publicly accessible via the Internet andcapable of serving as an internet proxy. Services capable of serving asan internet proxy, as used herein, may refer to a system or router thatprovides a gateway between users and the internet (e.g., network 105).In some embodiments, scanning system 101 of FIG. 1 may access aconfiguration detecting services over the internet and capable ofserving as an internet proxy.

Aspects of this disclosure may include embodiments configured tointegrate the identified services into the graph. Integrating identifiedservices into a graph, as used herein, may refer to the act of bringingtogether smaller components (the identified services) into a singlesystem that functions as one (the graph). For example, scanning system101 may integrate information on services available in each node intothe data structure, associated with each node in the data structure.

Aspects of this disclosure may include embodiments in which acloud-based cybersecurity system is configured to traverse the graph toidentify at least one source originating via the Internet and reachingthe workload. Traversing the graph, as used herein, may refer to adevice, such as scanning system 101, accessing the systems representedby the nodes in the graph, to determine which systems are accessible andhow. For example, scanning system 101 may analyze the graph to detectsources coming from the internet and reaching the workload, by accessinga first system, and traversing between systems in a depth-first,breadth-first, or other manner, until a path to an external network(e.g., the Internet) is reached.

In some embodiments, the at least one source may be a potentialmalicious source. In some embodiments, the source may include a code inany part of a software system or script that is intended to causeundesired effects, security breaches or damage to a system. (In someembodiments, the Internet at large may be considered to be a potentiallymalicious source.)

Aspects of this disclosure may include embodiments configured to outputa risk notification associated with the workload. Outputting a risknotification, as used herein, may refer to sending out data such as amessage indicating a possibility of danger. In some embodiments,scanning system 101 of FIG. 1 may produce a notification indicating arisk that is related with the workload. Examples of such risknotifications may include, for example, an electronic mail message, avisual alert, an audio alert, an audio-visual alert,

In some embodiments, the risk notification includes one or moreresolution recommendations. Resolution recommendations, as used herein,may refer to a suggestion or proposal as to the best course of action inview of the identified risk.

FIG. 6 illustrates a block diagram of method 600 performed by aprocessor (e.g., a processor associated with scanning system 101),consistent with disclosed embodiments. In some embodiments, theprocessor may operate on instructions stored in a non-transitorycomputer readable medium. In some embodiments, the method may includeseven (or more or less) steps:

Block 602: Access at least one cloud provider API to determine aplurality of entities capable of routing traffic in a virtual cloudenvironment associated with a target account containing the workload. Insome embodiments, scanning system 101 of FIG. 1 may determine entitiescapable of routing traffic, consistent with the above-disclosedembodiments.

Block 604: Query the at least one cloud provider API to determine atleast one networking configuration of the entities. In some embodiments,scanning system 101 of FIG. 1 may send a request to determine at leastone networking configuration of the entities, consistent with theabove-disclosed embodiments.

Block 606: Build a graph connecting the plurality of entities based onthe networking configuration. In some embodiments, scanning system 101of FIG. 1 may construct a graph or diagram linking the plurality ofentities based on the networking configuration, consistent with theabove-disclosed embodiments.

Block 608: Access a data structure identifying services publiclyaccessible via the Internet and capable of serving as an internet proxy.In some embodiments, scanning system 101 of FIG. 1 may access aconfiguration detecting services over the Internet and capable ofserving as an Internet proxy, consistent with the above-disclosedembodiments.

Block 610: Integrate the identified services into the graph. In someembodiments, scanning system 101 of FIG. 1 may incorporate the servicesinto the graph, consistent with the above-disclosed embodiments.

Block 612: Traverse the graph to identify at least one sourceoriginating via the Internet and reaching the workload. In someembodiments, scanning system 101 of FIG. 1 may analyze the graph todetect sources coming from the internet and reaching the workload,consistent with the above-disclosed embodiments.

Block 614: Output a risk notification associated with the workload. Insome embodiments, scanning system 101 of FIG. 1 may produce anotification indicating a risk that is related with the workload,consistent with the above-disclosed embodiments.

Techniques for Malware Detection Using Secondary System

Aspects of this disclosure may provide a technical solution to thechallenging technical problem of malware detection on a primary systemusing a secondary system other than the primary system. In existingtechnologies, malware detection system may be run on a primary systemthat itself may be susceptible to malware. The malware may detectexistence of the malware detection system and deceive it to avoid beingdetected. To resolve such a technical problem, a secondary system may beprovided to host the malware detection system, which may isolate themalware detection system from potential exposure or influence from themalware that may reside on the primary system. The disclosed technicalsolutions may increase success rate of malware detection and thusenhance security level of the primary system.

A cyber security system, as used herein, may refer to a system includingany combination of software and hardware for enhancing security of adevice, a platform, or another system in a network environment. By wayof example, the cyber security may be implemented as a system includingscanning system 101 in FIG. 1. As another example, scanning system 101may include the disclosed cyber security system as a subset. A cloudenvironment, as used herein, may refer to a computing environmentrunning on a cloud. By way of example, the cloud environment may includeor be part of cloud infrastructure 106 in FIG. 1.

Consistent with disclosed embodiments, at least one processor may beconfigured to utilize a cloud provider API to access a block storagevolume of a workload maintained on a target account in a target systemof a cloud storage environment. Utilizing, as used herein, may refer toan operation of using, deploying, enacting, enabling, activating,allocating, invoking, calling, or any operation of putting a thing intouse in a computer environment. An API refers to an applicationprogramming interface herein. A cloud provider in this disclosure mayrefer to a cloud service provider (e.g., a service provider of cloudcomputing, cloud storage, or any services provided to users on demandover a network). A cloud provider API, as used herein, may refer to anAPI provided, prepared, enabled, activated, programmed, or written by acloud provider. A block storage volume in this disclosure may refer to astorage volume in a block storage scheme. In some embodiments, a blockstorage volume may be connected, disconnected, or reconnected to asystem (e.g., a physical computer, a virtual machine, a networkinterface, a cloud, or any combination of hardware or software modules)without interfering (e.g., shutting down, halting, rebooting, or anymanner of interrupting) the operation status of the system or otherrunning tasks on the system. For example, a block storage volume may beimplemented as a virtual disk. In some embodiments, a block storagevolume can be associated with an account of a user of the system, thesystem that it is connected to, or both.

Block storage, as used herein, may refer to a data storage scheme ormodel in which data is saved to storage media in fixed-sized raw datachunks (referred to as “blocks”). The raw data blocks may contain nometadata. Each block may be associated with a unique address as metadataassigned to the block. Storage blocks may be controlled by an operatingsystem (OS) and may be accessed by a protocol (e.g., iSCSI, FibreChannel, or Fibre Channel over Ethernet).

A storage volume, as used herein, may refer to an identifiable unit(e.g., a physical unit or a logical, virtual unit) of data storage. Thestorage volume may be mounted to a device via an operation system and beconfigured with a specific file system (e.g., New Technology FileSystem) assigned a system-unique name or number that identifies thestorage volume. The storage volume may represent a named, logical areaof storage that enables users and applications to access data on theunderlying device. By way of example, a storage volume may be a logicaldisk that represents a named, logical area of a physical storage device(e.g., a hard disk drive, solid-state drive, compact disc read-onlymemory, digital video disk, floppy disk, or any other type of storagedevice). In some embodiments, a logical storage volume may span multiplephysical storage devices (e.g., hard disks) and appear as a single,contiguous storage area that works like a physical volume. Storagevolumes may be flexibly configured, such as being expanded, contracted,mirrored, stripped, or adapted to support multiple disks (e.g.,redundant array of independent disks).

A workload, as used herein, may refer to a specific application,service, capability, or a specific amount of work that can be run on acloud resource, system, or infrastructure. By way of example, a workloadmay be a virtual machine, a database, a container, a Hadoop node, anapplication, a storage object, a load balancer, or an IAM (Identity andAccess Management) configuration. A cloud storage environment in thisdisclosure may refer to a computing environment of a cloud computingmodel (referred to as “cloud storage”) that stores data on the Internetthrough a cloud computing provider that manages and operates datastorage as a service. A cloud storage environment may be managed andcontrolled by an operating system. The operation system may besusceptible to malware and security vulnerabilities, and may become aprimary system (or referred to as a “target system” herein) that needsmalware detection. By way of example, the cloud storage environment mayinclude or be part of cloud infrastructure 106 in FIG. 1.

A target system of a cloud storage environment in this disclosure mayrefer to an operating system or a computing system with an installedoperating system, which manages and controls the cloud storageenvironment or a subsystem of the target system. The target system maymaintain one or more accounts for users of the cloud storageenvironment. A target account of the target system in this disclosuremay refer to an account of a user of a cloud infrastructure (e.g., acloud environment or a cloud storage environment).

By way of example, to utilize the cloud provider API to access the blockstorage volume (e.g., existing in storage 111A-111D in FIG. 1) of theworkload, the at least one processor (e.g., a processor in scanningsystem 101 of FIG. 1) may communicate with the cloud storage environment(e.g., cloud infrastructure 106 in FIG. 1) via sending and receivingdata (e.g., data packets) over a network (e.g., network 105 in FIG. 1),and enable one or more APIs provided by the cloud provider for accessingthe block storage volume. For example, the communication and APIenabling may be performed through the process of integration asdescribed in step 201 of FIG. 2. In some embodiments, the at least oneprocessor may create a connection (e.g., by logging in) between a firstaccount on scanning system 101 and a second account on cloudinfrastructure 106, then cause the second account to authorize accessprivileges to the first account via the cloud provider API for accessingstorage 111A-111D in cloud infrastructure 106.

Consistent with disclosed embodiments, the at least one processor may beconfigured to utilize a scanner at a location of the block storagevolume and on a secondary system other than the target system. Ascanner, as used herein, may refer to an application, a program, aservice, a process, a thread, a function, or any executable codes forperforming a scanning process on a computer system to obtain information(e.g., related to structures, vulnerabilities, security issues, or anyinformation of the computer system).

A location of the block storage volume in this disclosure may refer to asystem (e.g., a physical computer, a virtual machine, a networkinterface, a cloud, a data center, or any combination of hardware orsoftware modules) or an identifier associated with the system that theblock storage volume is connected to. In some embodiments, the locationof the block storage volume may include at least one of the targetaccount, a secondary system account, a cloud provider account, or athird party account. By way of example, the secondary system account maybe an account connected with the target account (e.g., connected by anintegration process similar to step 201 in FIG. 2A). The cloud provideraccount may be an account connected to at least one of the targetaccount or the secondary system account. The third party account may bean account hold by a third party and connected to at least one of thetarget account, the secondary system account, or the cloud provideraccount.

In some embodiments, the at least one processor may determine thelocation of the block storage volume based on at least one of the targetaccount, a secondary system account, a cloud provider account, or athird party account. By way of example, to determine the location of theblock storage volume, the at least one processor may consult a lookuptable, a list, or a database that stores a relationship record betweenan account (e.g., a target account, a secondary system account, a cloudprovider account, or a third party account) and a system (e.g., aphysical computer, a virtual machine, a network interface, a cloud, orany combination of hardware or software modules) that the block storagevolume is connected to. Based on the relationship record, the at leastone processor may identify the system as the location using the accountas a key.

A secondary system, as used herein, may refer to a computer systemrunning at an environment or conditions not affected by another system(referred to as a “primary system” or “target system” herein). In someembodiments, the secondary system may have an operating system differentfrom an operating system of the target account. By way of example, thetarget account may have a WINDOWS® operating system, and the secondarysystem may have a LINUX® operating system.

In some embodiments, the secondary system includes at least one of avirtual machine (e.g., any of virtual machines 107A-107D in FIG. 1), acontainer, or a serverless function. A container, as used herein, mayrefer to an OS-level virtualization instance assigned with resources bya non-virtual computer operating system (OS). A non-virtual computeroperating system (OS) may create multiple isolated user space instancesthat may function like real computers from the point of view of programsrunning in them. A computer program running on a non-virtual operatingsystem can access all available resources (e.g., connected devices,files, folders, network shares, CPU power, or any other software orhardware capabilities) of the computer. In contrast, a computer programrunning inside of a container can only access the resources assigned tothe container.

A serverless function, as used herein, may refer to a computer functionhosted in a cloud environment that may allocate resources on demand toperform a function (e.g., scanning) for a user of the cloud environment.The user of the serverless function may be free from concerns ofcapacity planning, configuration, management, maintenance, faulttolerance, or scaling of containers, virtual machines, or physicalservers. When a serverless function is not running, no computingresources may be allocated to it (e.g., using no provisioned server,thus named “serverless”). By way of example, a serverless function maybe implemented as any combination of Lambda functions, event sources,and other computing resources. A serverless function may be invoked bythe user of a cloud infrastructure (e.g., a cloud environment or a cloudenvironment).

By way of example, to utilize the scanner at the location of the blockstorage volume (e.g., existing in storage 111A-111D in FIG. 1), the atleast one processor (e.g., a processor in scanning system 101 of FIG. 1)may communicate with the secondary system (e.g., one or more of virtualmachines 107A-107D in FIG. 1) other than the target system (e.g., themain system operating and managing storage 111A-111D) and activate thesecondary system for scanning. For example, to activate the secondarysystem, the at least one processor may transmit a scanner (e.g., in theform of a computer program or executable codes) to the secondary system,and the secondary system may allocate computing resources (e.g., CPUpowers, memory space, network ports, or any other software or hardwareresources) in preparation of running the scanner. The scanner may beprogrammed to be stored at the location of the block storage volume orto start the scanning at the location of the block storage volume. Forexample, the block storage volume may be connected to a particularsystem in cloud infrastructure 106 in FIG. 1, and the scanner may bestored at that system (e.g., on storage connected to the system). Whenthe scanner begins scanning, the scanner may start the scanning at thatsystem before scanning other systems.

In some embodiments, to utilize the scanner, the at least one processormay suspend an operation of the scanner after the scan of the blockstorage volume. Suspending, as used herein, may refer to an operation ofpausing, stopping, ceasing, freezing, halting, hanging, terminating,killing, or any manner or temporarily or permanently setting aside anongoing process or computer program. By way of example, after thescanner completes scanning the block storage volume, the at least oneprocessor may detect the completion by an active manner (e.g., byperiodically polling the secondary system for a status of the scanning)or a passive manner (e.g., by receiving a message from the secondarysystem indicating the completion of the scanning). The at least oneprocess may then send data to the secondary system, the data including asignal or computer-executable codes for suspending the operation of thescanner. After receiving the data, the secondary system may suspend thescanner and release the computing resources previously allocated to thescanner.

In some embodiments, to utilize the scanner, the at least one processormay modify a pre-utilized scanner at the location of the block storagevolume based on information related to the target account to obtain amodified scanner, and then utilize the modified scanner. A pre-utilizedscanner in this disclosure may refer to a scanner that has beenpreviously utilized (e.g., on the same secondary system) and notdestroyed. In some embodiments, the information related to the targetaccount may include data or parameters indicating a status or a changeof the target account, such as, for example, newly created files,deleted files, changed files, or any data indicating a state of thetarget account. For example, the pre-utilized scanner at the blockstorage volume may use a configuration file. The configuration file mayinclude data or parameters indicating a previous status (e.g., list ofexisting files, public network ports, Internet-accessible data channels,or any operation state parameters) of the target account. Theinformation related to the target account may include data indicating acurrent status of the target system. The current status of the targetsystem may be different from the previous status of the target system(e.g., including changed files, changed public network ports, changedInternet-accessible data channels, or any changed operation stateparameters). The at least one processor may modify the pre-utilizedscanner by modifying the configuration file to reflect the currentstatus of the target system. Then, the at least one processor mayutilize the modified scanner.

Consistent with disclosed embodiments, the at least one processor may beconfigured to scan the block storage volume for malicious code, usingthe secondary system. Scanning, as used herein, may refer to anoperation of traversing, checking, inspecting, reading, examining,searching, or any manner of looking up. Malicious code, as used herein,may refer to an application, a computer program, a service, a process, athread, a function, a script, or any type of executable codes that maybe executed on a computer without authorization and with a malicious orharmful intent (e.g., manipulating the computer into dangerousbehaviors, writing changes or add-ons to existing computer programs orfiles, stealing computer files, copying sensitive information withoutauthorization, damaging the computer itself, disabling one or morefunctions of the computer, or attacking another computer using thecomputer as a disguise). For example, malicious code may include attackscripts, computer viruses, computer worms, Trojan horses, backdoors, orany other malicious executable content. In some embodiments, themalicious code may include a rootkit. A rootkit in this disclosure mayrefer to any type of computer software designed to enable access to acomputer or an area of its software without authorization.

By way of example, to scan the block storage volume (e.g., existing instorage 111A-111D in FIG. 1) for malicious code, the secondary system(e.g., one or more of virtual machines 107A-107D in FIG. 1) may run theutilized scanner with allocated computing resources to look up databases(e.g., a blacklist) of known malicious files, look up databases storingpatterns of malicious files and identify the patterns, look up databasesof cryptographic hashes that identify malicious files, run potentialmalicious code in a sandbox (e.g., a confined and isolated environmentfor running programs without causing changes outside the confined andisolated environment), determine whether there are scanned files thatare not in a database (e.g., a whitelist) of known good files, detectchanges over time in the scanned environment, or any combinationthereof.

In some embodiments, scanning the block storage volume may includescanning disk-backed memory. A disk-backed memory in this disclosure mayrefer to a storage space implemented on a disk (e.g., a hard disk) andfunctioning like a volatile memory from the perspective of a runningprogram. By way of example, scanning the block storage volume mayinclude scanning files stored in the disk-backed memory. In someembodiments, the disk-backed memory may include at least one of a pagefile or a cache file. A page file, as used herein, may refer to a filecontaining one or more pages (also referred to as “memory pages” or“virtual pages”), each of the one or more pages being a fixed-lengthcontiguous block of virtual memory and described by a single entry in apage table. A page file may be stored on a disk (e.g., a hard disk) formemory management of a virtual memory used by an operating system. Acache file, as used herein, may refer to a file storing data so thatfuture requests for the stored data can be served faster. The datastored in a cache file may be the result of a computation or a copy ofthe data stored elsewhere.

Consistent with disclosed embodiments, the at least one processor may beconfigured to identify malicious code based on the scan. By way ofexample, if the secondary system scans the block storage volume byconsulting databases of known malicious files and finds a scanned filematches a record in the databases, the at least one processor mayidentify the matched scanned file as the malicious code. In anotherexample, if the secondary system scans the block storage volume byconsulting databases storing patterns of malicious files and identifiesa pattern of a scanned file matches one or more of the stored patterns,the at least one processor may identify the scanned file as themalicious code. In yet another example, if the secondary system scan theblock storage volume by consulting databases of cryptographic hashesthat identify malicious files and finds that a cryptographic hash of ascanned file matches one or more of the cryptographic hashes thatidentify malicious files, the at least one processor may identify thescanned file as the malicious code.

In yet another example, if the secondary system scans the block storagevolume by running potential malicious code in a sandbox and finds thatrunning a scanned file causes malicious or harmful changes or behavior(e.g., an attempt to modify a system setting, an attempt to access filesoutside of a set of directories, an attempt to perform a network mappingprocess), the at least one processor may identify the scanned file asthe malicious code. In yet another example, if the secondary systemscans the block storage volume to determine whether there are scannedfiles that are not in a database of known good files and finds that ascanned file is not in the database of known good files, the at leastone processor may identify the scanned file as the malicious code. Asyet another example, if the secondary system scans the block storagevolume to detect changes over time in the scanned environment andfinding that a scanned file causes a malicious or harmful change in thescanned environment over time, the at least one processor may identifythe scanned file as the malicious code. It should be noted that theidentification of the malicious code based on the scan may beimplemented in various manners and is not limited to the examplesdescribed herein.

Consistent with disclosed embodiments, the at least one processor may beconfigured to output from the secondary system, a notification of apresence of malicious code in the target system. In some embodiments,the notification may be a pop-up window, a pop-pup dialog, a flashingsymbol, an email, a text message, a mobile application notice, a phonecall, a warning sound, a tactile feedback (e.g., a vibration), or anytype of communications. By way of example, the secondary system maytrigger a communication channel between the secondary system and thetarget system and feed one or more parameters to the communicationchannel, in which the one or more parameters represent the presence ofthe malicious code. The secondary system may then send data representingthe notification via the triggered communication channel including theone or more parameters to the target system. After receiving the data,the target system may parse the data and identify the one or moreparameters. The target system may then display the notification (e.g.,as a pop-up window on a screen) that present the presence of themalicious code.

Consistent with disclosed embodiments, the at least one processor may befurther configured to identify a source of the malicious code. Thenotification of the presence of malicious code outputted from thesecondary system in the target system may include information related tothe identified source of the malicious code. In some embodiments, thesource of the malicious code may include identity of a developer ordistributor of the malicious code, the landing location (e.g., a networkport or a vulnerable access point) where the malicious code is importedto the target system, source codes of the malicious code, or anyinformation or data indicating the origination of the malicious code.The information related to the identified source of the malicious codemay include a text, a picture, a symbol, a video, a link, a voice, orany type of data for presenting and describing the identified source ofthe malicious code.

By way of example, FIG. 7 is a block diagram illustrating an exemplaryprocess 300 of cyber security scanning for a cloud environment,consistent with the disclosed embodiments. While the block diagram maybe described below in connection with certain implementation embodimentspresented in other figures, those implementations are provided forillustrative purposes only, and are not intended to serve as alimitation on the block diagram. For example, the steps in FIG. 7 may beexecuted in any order, steps may be duplicated, or steps may be omitted.In some embodiments, the process 300 may be performed by at least oneprocessor (e.g., a CPU) of a computing device or system (e.g., scanningsystem 101 in FIG. 1) to perform operations or functions describedherein, and may be described hereinafter with reference to FIGS. 1-2D byway of example. In some embodiments, some aspects of the process 300 maybe implemented as software (e.g., program codes or instructions) thatare stored in a memory or a non-transitory computer-readable medium. Insome embodiments, some aspects of the process 300 may be implemented ashardware (e.g., a specific-purpose circuit). In some embodiments, theprocess 700 may be implemented as a combination of software andhardware.

FIG. 7 includes process blocks 702-710. At block 702, at least oneprocessor may utilize a cloud provider API to access a block storagevolume of a workload maintained on a target account in a target systemof a cloud storage environment.

At block 704, the at least one processor may utilize a scanner at alocation of the block storage volume and on a secondary system otherthan the target system. In some embodiments, the secondary system mayinclude at least one of a virtual machine, a container, or a serverlessfunction. In some embodiments, the secondary system may have anoperating system different from an operating system of the targetaccount.

In some embodiments, to utilize the scanner, the at least one processormay suspend an operation of the scanner after the scan of the blockstorage volume. In some embodiments, to utilize the scanner, the atleast one processor may modify a pre-utilized scanner at the location ofthe block storage volume based on information related to the targetaccount to obtain a modified scanner, and the utilize the modifiedscanner.

At block 706, the at least one processor may scan the block storagevolume for malicious code, using the secondary system. In someembodiments, to scan the block storage volume, the at least oneprocessor may scan disk-backed memory. For example, the disk-backedmemory includes at least one of a page file or a cache file. In someembodiments, the malicious code includes a rootkit.

At block 708, the at least one processor may identify malicious codebased on the scan. At block 710, the at least one processor may outputfrom the secondary system, a notification of a presence of maliciouscode in the target system.

Consistent with disclosed embodiments, besides blocks 702-710, the atleast one processor may further determine the location of the blockstorage volume based on at least one of the target account, a secondarysystem account, a cloud provider account, or a third party account.

Consistent with disclosed embodiments, besides blocks 302-310, the atleast one processor may further identify a source of the malicious code.The notification outputted in block 710 may include information relatedto the identified source of the malicious code.

Forward and Rearward Facing Attack Vector Visualization Techniques

FIG. 8 is a schematic block diagram illustrating an exemplary embodimentof a system for performing visualization of forward and backward facingthreats.

In one of many embodiments, the system may include a graphical userinterface system for providing forward and backward facing attack vectorvisualizations. A graphical user interface system may include systemssimilar in appearance and functionality to Microsoft Windows, Mac OS,Ubuntu Unity, Gnome Shell, Android, Apple iOS, Blackberry OS, Windows 10Mobile, PalmOS-Web OS, or Firefox OS. Forward facing attack vectors maybe those external entities that may access an analyzed asset. Backwardfacing attack vectors may include the possible impacts to an analyzedasset and those impacts' possible effect. Visualizations provided by theabove system may include graphical, sequential, or multi-dimensionaldisplays of attack vectors.

In an embodiment, the system may comprise at least one processorconfigured to identify assets 801 in a cloud environment. The at leastone processor may include a processor such as user device 102 of FIG. 1.The at least one processor may include a personal computer, tablet,smartphone, or virtual machine for processing threats andvulnerabilities to a cloud-based storage volume. For example, cloudinfrastructure 106 may be the cloud environment consisting of virtualmachines 107A-107D, databases 109A-109D, storage 111A-111D, keystores113A-113D, and load balancer 115, and the cloud-based storage volume maybe contained in storage 111A-111D. The cloud environment may includeservice provided by a third party such as Amazon Web Services, MicrosoftAzure, Google Cloud, Alibaba Cloud, IBM Cloud, Oracle, Salesforce, SAP,or similar service.

Another embodiment contemplated may consist of at least one processorconfigured to identify risks 803 associated with each of the identifiedasset. The identified risks 803 associated with each of the identifiedassets may be listed sequentially based on probability of risk, severityof risk, or similar method of ordering the risks. The identified risks303 associated with an identified asset may be scored based on the levelof risk to the asset and may be categorized as a high risk, medium risk,or low risk. Once the level of risk can be determined by scanning system101, the level of risk can be conveyed and displayed to a user device102 with a representative graphical display.

An exemplar embodiment may additionally comprise at least one processorconfigured to identify relationships 805 between at least some of theidentified assets, the relationships including at least one of a trust807A, a network connectivity 807B, or a mechanism of network proxying807C. A trust 807A may establish a relationship and may involvecryptography, digital signatures, electronic certificates, or similarmethod of establishing a trusting relationship. A network connectivity807B may include wireless or wired connections and may be establishedonce a relationship of trust 807A is established. A mechanism of networkproxying 807C can be accommodated once trust 807A and networkconnectivity 807B are established through any number of connectedservers to accomplish proxying.

A further embodiment may also comprise a processor configured to receivean identification 809 of a specific asset under investigation. Thespecific asset under investigation may be a physical or virtual machinethat has software operating a specific version that is vulnerable to anynumber of associated risks. The identification 809 of a specific assetunder investigation may involve an IP address, universally uniqueidentifier, or similar system to uniquely or semi-uniquely identify thespecific asset under investigation.

A system among several embodiments may include a processor configured toperform a forward analysis 811A of the specific asset underinvestigation to identify at least one possible attack vector reachingthe specific asset via a network outside the cloud environment. Aforward analysis 811A of the specific asset may involve those externalentities that may access an analyzed asset. The analysis performed byscanning system 101 may determine the origin of the forward threat, thenature of the threat to the analyzed system, and the seriousness of thethreat originating from the Internet. For example, scanning system 101may identify at least one possible attack vector to the workloadcurrently being analyzed. The network outside of the cloud environmentmay identify new or existing threats and attack vectors currentlythreatening the associated system and workload.

An exemplary embodiment may further comprise a processor configured toperform a backward analysis 811B of the specific asset to identify atleast one exposure risk to one or more assets that is in a downstream ofthe specific asset, wherein the at least one exposure risk includes anidentification of an exposed asset, an entry point to the exposed asset,and a lateral movement risk associated with the exposed asset. Abackward analysis 811B of the associated machine may look downstream torelated workloads and systems connected to the analyzed systems. A scandownstream may involve, among several embodiments, the downstreamexposure risk including an identification of an exposed asset, an entrypoint to the exposed asset, and lateral movement risks associated withthe exposed asset. The at least one exposure risk may include one ormore entry point to access the exposed asset and any related machinespotentially vulnerable to attack from the analyzed and exposed asset.

Another embodiment may comprise a processor configured to output asignal 813 to cause on a display to present a presentation of forwardand backward paths associated with the specific asset, thereby enablingvisualization of a plurality of entry points and lateral movement risksassociated with the plurality of entry points. The display of a forwardor backward path to a specific asset may be one of several visualdisplays such as linear, graphical, or through computer-generatedimages. The visualization of a plurality of entry points and lateralmovement risks with the plurality of entry points may includevisualization of the plurality of paths may sequence the paths based onlikelihood of access via that path or the severity of potential threatin a path of access to an asset.

An example embodiment may comprise a system wherein the network outsidethe cloud environment includes the Internet. The network outside thecloud environment may include access to the Internet in order for thesystem to access a plurality of analyzed and potentially vulnerableassets.

Another embodiment may comprise a system wherein the assets in the cloudenvironment include at least one of a virtual machine, a networkappliance, a storage appliance, a compute instance, or an engineinstance. A virtual machine may include an emulated version of acomputer—including an operating system, memory, storage, graphicsprocessing—such that it can be indistinguishable from a standard(non-virtual) machine to a running program. A network appliance mayinclude a plurality of servers connected through the Internet in orderto establish a system and network of stored assets and workloads. Astorage appliance may be comprised by a server designed to storeworkloads and assets to be analyzed. A compute instance may involveinput and processing of data entries that cause the analyzed asset to beaccessed and run. An engine instance may include a search algorithm runto analyze and search the analyzed workloads or virtual machines todetermine the software and data stored on the said virtual machine orstored instance.

One among many embodiments may comprise a system wherein identifying theassets in a cloud environment includes identifying the assets based onat least one of an identity and access management policy, anorganization policy, or an access policy. An identity and accessmanagement policy may comprise a software tool or similar method ofestablishing identity of users attempting to access a system to verifyidentities of users and control access to an associated workload orsystem functionality. An organization policy may include a policyapplied to all users by the controlling organization of a workload. Anaccess policy may determine the authorized users of an associatedsystem.

One possible embodiment may comprise a system wherein the presentationof the forward and backward paths indicates alternative paths connectingbetween the specific asset and an upstream asset or a downstream asset.The indication will be via a visualization showing specific alternativepaths connecting specific assets or it may visualize a plurality ofalternative paths connecting specific assets. Alternative pathsconnecting between the specific asset and an upstream asset or adownstream asset may involve a direct connection, such as via theInternet, or an indirect connection via one or more series of serversacting as proxy servers between the analyzed asset and the upstream ordownstream asset.

An exemplary embodiment may further comprise a system wherein thevisualization includes a presentation of the alternative paths. Thealternative paths may be presented visually through a graphicalrepresentation, sequential list of alternative paths, or acomputer-generated image that represents the plurality of alternativepaths.

Another embodiment may comprise a system wherein the presentation of theforward and backward paths indicates port numbers for each pathway. Theport numbers may be indicated by a series of alphanumeric characters(e.g., “HTTP” or “80”) or other identifier.

One among several exemplary embodiments may further comprise a systemwherein the visualization of the entry points indicates at least oneentry point of risk. The visualization may indicate one or more pointsof entry to a given analyzed system. An entry point of risk may involvea port of access to the workload, and may involve a one or more entrypoints visualized for use by user device 102.

Another exemplary embodiment may comprise a system wherein the at leastone processor is further configured to monitor network activities of theassets in a cloud environment. The processor may monitor continuously,intermittently, or as directed by an authorized user to directmonitoring of the analyzed network activities of the assets. The cloudenvironment may be, among several embodiments, the cloud infrastructure106.

An embodiment contemplated may comprise a system further configured todetect a potential risk associated with the specific asset based on anetwork activity of the specific asset. The potential risk may beassociated to a specific asset based on historical threats to thespecific asset or a list of possible threats to the specific asset basedon its current network activities.

Another embodiment may comprise a system further configured to detect apotential risk associated with the specific asset based on a networkactivity of an upstream asset of the specific asset. The potential riskassociated with the specific asset may be identified by scanning system101 and determine whether a potential risk can be classified as highrisk, medium risk, or low risk. The potential risk may be identifiedbased on the specific asset, the network activity performed by thespecific asset, or the specific asset type or related software of theupstream asset.

One of many embodiments may comprise a system further configured todetect a potential risk associated with the specific asset based on anetwork activity of a downstream asset of the specific asset. Thepotential risk may be identified based on the specific asset, thenetwork activity performed by the specific asset, or the specific assettype or related software of the upstream asset. For example, scanningsystem 101 may perform a scan on an asset being analyzed, and based onthe one or more entry points of risk, may determine if the downstreamasset of the specific asset poses a potential risk to the analyzedsystem.

Another exemplary embodiment may comprise a method for generating agraphical user interface for providing forward and backward facingattack vector visualizations. The method may include a method ofgenerating a graphical user interface similar in appearance andfunctionality to Microsoft Windows, Mac OS, Ubuntu Unity, Gnome Shell,Android, Apple iOS, Blackberry OS, Windows 10 Mobile, PalmOS-Web OS, orFirefox OS. A forward analysis 811A of the specific asset may involvethose external entities that may access an analyzed asset. Backwardanalysis 811B may include the possible impacts to an analyzed asset andthose impacts' possible effect. Visualizations provided by the abovesystem may include graphical, sequential, or multi-dimensional displaysof attack vectors.

One exemplar embodiment may further comprise a method of identifyingassets 801 in a cloud environment. A method may include at least oneprocessor that may include a personal computer, tablet, smartphone, orvirtual machine for processing threats and vulnerabilities to acloud-based storage volume. For example, cloud infrastructure 106 may bethe cloud environment consisting of virtual machines 107A-107D,databases 109A-109D, storage 111A-111D, keystores 113A-113D, and loadbalancer 115, and the cloud-based storage volume may be contained instorage 111A-111D. The cloud environment may include service provided bya third party such as Amazon Web Services, Microsoft Azure, GoogleCloud, Alibaba Cloud, IBM Cloud, Oracle, Salesforce, SAP, or similarservice.

One of several embodiments may comprise a method of identifying risks803 associated with each of the identified assets 801. The method ofidentifying risks 803 associated with each of the identified assets 801may be listed sequentially based on probability of risk, severity ofrisk, or similar method of ordering the risks. The identified risks 803associated with an identified asset may be scored based on the level ofrisk to the asset and may be categorized as a high risk, medium risk, orlow risk. Once the level of risk can be determined by scanning system101, the level of risk can be conveyed and displayed to a user device102 with a representative graphical display.

Another embodiment contemplated may comprise a method for identifyingrelationships 305 between at least some of the identified assets 801,the relationships including at least one of a trust 807A, a networkconnectivity 807B, or a mechanism of network proxying 807C. A trust 807Amay establish a relationship and may involve cryptography, digitalsignatures, electronic certificates, or similar method of establishing atrusting relationship. A network connectivity 807B may include wirelessor wired connections and may be established once a relationship of trust807A is established. A mechanism of network proxying 807C can beaccommodated once trust 807A and network connectivity 807B areestablished through any number of connected servers to accomplishproxying.

An embodiment may further comprise a method of receiving anidentification of a specific asset 809 under investigation. The specificasset under investigation may be a physical or virtual machine that hassoftware operating a specific version that is vulnerable to any numberof associated risks 803. The identification 809 of a specific assetunder investigation may involve an IP address, universally uniqueidentifier, or similar system to uniquely or semi-uniquely identify thespecific asset under investigation.

An embodiment may also comprise a method of performing a forwardanalysis 811A of the specific asset under investigation to identify atleast one possible attack vector reaching the specific asset via anetwork outside the cloud environment. A forward analysis 811A of thespecific asset may involve those external entities that may access ananalyzed asset. A forward analysis may involve analysis of the specificasset under identification to identify at least one possibleInternet-originating attack vector to the asset. The analysis performedby scanning system 101 may determine the origin of the forward threat,the nature of the threat to the analyzed system, and the seriousness ofthe threat originating from the Internet. For example, scanning system101 may identify at least one possible attack vector to the workloadcurrently being analyzed. The network outside of the cloud environmentmay identify new or existing threats and attack vectors currentlythreatening the associated system and workload.

One embodiment may comprise a method of performing a backward analysis811B of the specific asset to identify at least one exposure risk to oneor more assets that is in a downstream of the specific asset, whereinthe at least one exposure risk includes an identification of an exposedasset, an entry point to the exposed asset, and a lateral movement riskassociated with the exposed asset. Backward analysis 811B may includethe possible impacts to an analyzed asset and those impacts' possibleeffect. A scan downstream may involve, among several embodiments, thedownstream exposure risk including an identification of an exposedasset, an entry point to the exposed asset, and lateral movement risksassociated with the exposed asset. The at least one exposure risk mayinclude one or more entry point to access the exposed asset and anyrelated machines potentially vulnerable to attack from the analyzed andexposed asset.

An embodiment may comprise a method of outputting a signal 813 to causeon a display to present a presentation of forward and backward pathsassociated with the specific asset, thereby enabling visualization of aplurality of entry points and lateral movement risks associated with theplurality of entry points. The display of a forward or backward path toa specific asset may be one of several visual displays such as linear,graphical, or through computer-generated images. The visualization of aplurality of entry points and lateral movement risks with the pluralityof entry points may include visualization of the plurality of paths maysequence the paths based on likelihood of access via that path or theseverity of potential threat in a path of access to an asset.

Another embodiment may comprise a method wherein the network outside thecloud environment includes the Internet. The network outside the cloudenvironment may include access to the Internet in order for the systemto access a plurality of analyzed and potentially vulnerable assets.

One of several embodiments may comprise a method wherein the assets inthe cloud environment include at least one of a virtual machine, anetwork appliance, a storage appliance, a compute instance, or an engineinstance. A virtual machine may include an emulated version of acomputer—including an operating system, memory, storage, graphicsprocessing—such that it can be indistinguishable from a standard(non-virtual) machine to a running program. A network appliance mayinclude a plurality of servers connected through the Internet in orderto establish a system and network of stored assets and workloads. Astorage appliance may be comprised by a server designed to storeworkloads and assets to be analyzed. A compute instance may involveinput and processing of data entries that cause the analyzed asset to beaccessed and run. An engine instance may include a search algorithm runto analyze and search the analyzed workloads or virtual machines todetermine the software and data stored on the said virtual machine orstored instance.

An embodiment may further comprise a method wherein identifying assetsin a cloud environment includes identifying the assets based on at leastone of an identity and access management policy, an organization policy,or an access policy. An identity and access management policy maycomprise a software tool to verify identities of users and controlaccess to an associated workload or system functionality. Anorganization policy may include a policy applied to all users by thecontrolling organization of a workload. An access policy may determinethe authorized users of an associated system.

An embodiment may also comprise a method wherein the presentation of theforward and backward paths indicates alternative paths connectingbetween the specific asset and an upstream or a downstream asset. Theindication may be via a visualization showing specific alternative pathsconnecting specific assets or it may visualize a plurality ofalternative paths connecting specific assets.

Another exemplar embodiment may comprise a method wherein thevisualization includes a presentation of the alternative paths. Thealternative paths may be presented visually through a graphicalrepresentation, sequential list of alternative paths, or acomputer-generated image that represents the plurality of alternativepaths.

Another embodiment may comprise a non-transitory computer-readablemedium storing instructions that, when executed by at least oneprocessor, are configured to cause the at least one processor to performoperations.

One embodiment may comprise a non-transitory computer-readable mediumstoring instructions that, when executed by at least one processor 800,are configured to perform operations identifying assets 801 in a cloudenvironment. the instructions stored on a non-transitorycomputer-readable medium may include at least one processor 800 that mayinclude a personal computer, tablet, smartphone, or virtual machine forprocessing threats and vulnerabilities to a cloud-based storage volume.The cloud environment may include service provided by a third party suchas Amazon Web Services, Microsoft Azure, Google Cloud, Alibaba Cloud,IBM Cloud, Oracle, Salesforce, SAP, or similar service.

An embodiment may further comprise a non-transitory computer-readablemedium storing instructions that, when executed by at least oneprocessor, are configured to cause the at least one processor 300 toperform operations comprising identifying risks 803 associated with eachof the identified asset. The instructions performed of identifying risks803 associated with each of the identified assets 301 may be listedsequentially based on probability of risk, severity of risk, or similarmethod of ordering the risks.

Another embodiment may comprise a non-transitory computer-readablemedium storing instructions that, when executed by at least oneprocessor, are configured to cause the at least one processor to performoperations comprising identifying relationships 805 between at leastsome of the identified assets 301, the relationships including at leastone of a trust 807A, network connectivity 807B, or a mechanism ofnetwork proxying 807C.

An exemplar embodiment may comprise a non-transitory computer-readablemedium storing instructions that, when executed by at least oneprocessor, are configured to cause the at least one processor to performoperations comprising receiving an identification of a specific asset809 under investigation. The instructions may include receivinginformation identifying the specific asset 809. The specific asset 809under investigation may be a physical or virtual machine that hassoftware operating a specific version that is vulnerable to any numberof associated risks 803.

One among many embodiments may comprise a non-transitorycomputer-readable medium storing instructions that, when executed by atleast one processor, are configured to cause the at least one processorto perform operations comprising performing a forward analysis 811A ofthe specific asset under investigation to identify at least one possibleattack vector reaching the specific asset via a network outside thecloud environment. A forward analysis 811A of the specific asset mayinvolve those external entities that may access an analyzed asset. Andthe scanning system 101 may identify at least one possible attack vectorto the workload currently being analyzed. The network outside of thecloud environment may identify new or existing threats and attackvectors currently threatening the associated system and workload.

An embodiment may further comprise a non-transitory computer-readablemedium storing instructions that, when executed by at least oneprocessor, are configured to cause the at least one processor to performoperations comprising performing a backward analysis 811B of thespecific asset to identify at least one exposure risk to one or moreassets that is in a downstream of the specific asset, wherein the atleast one exposure risk includes an identification of an exposed asset,an entry point to the exposed asset, and a lateral movement riskassociated with the exposed asset. Backward analysis 811B may includethe possible impacts to an analyzed asset and those impacts' possibleeffect. The at least one exposure risk may include one or more entrypoint to access the exposed asset and any related machines potentiallyvulnerable to attack from the analyzed and exposed asset.

An embodiment may comprise a non-transitory computer-readable mediumstoring instructions that, when executed by at least one processor, areconfigured to cause the at least one processor to perform operationscomprising outputting a signal 813 to cause on a display to present apresentation of forward and backward paths associated with the specificasset, thereby enabling visualization of a plurality of entry points andlateral movement risks associated with the plurality of entry points.The display of a forward or backward path to a specific asset may be oneof several visual displays such as linear, graphical, or throughcomputer-generated images. The visualization of a plurality of entrypoints and lateral movement risks with the plurality of entry points mayinclude visualization of the plurality of paths may sequence the pathsbased on likelihood of access via that path or the severity of potentialthreat in a path of access to an asset.

Passive Key Identification Techniques

Aspects of this disclosure may provide a technical solution to thechallenging technical problem of identifying access keys (e.g.,passwords, Secure Shell (SSH) keys, or cloud keys) to compute resources(e.g., machines, containers, storages, or any hardware or softwarecomponent) in a cloud environment without using the access keys toaccess the compute resources. In existing technologies, scanning systemsmay identify access keys to compute resources and may need to verify theidentified keys by actually accessing the compute resources using theaccess keys. In such cases, the actual accesses may generate logs orrecords (e.g., for successful or failed accesses) that can constituteactivity patterns similar to an attacker to the system. Such activitypatterns may distract a system administrator (e.g., an individual or acomputer program) to misidentify the scanning system as an attacker.Further, actual accesses may create loads on both the scanning systemand the compute resources and may reduce the computing resources andpower for other tasks. To resolve such a technical problem, acryptographic analysis may be performed to identify a first set offingerprints of the identified keys, and trust configurations of thecompute resources may be analyzed to identify a second set offingerprints of the compute resources. The first and second set offingerprints may be compared to match keys with the compute resourceswithout using the keys to access the compute resources. By doing so, thescanning system may perform its function without raising false alarms tothe system administrator, while reducing computing costs to the cloudenvironment.

A cyber security system, as used herein, may refer to a system includingany combination of software and hardware for enhancing security of adevice, a platform, or another system in a network environment. By wayof example, the cyber security may be implemented as a system includingscanning system 101 in FIG. 1. As another example, scanning system 101may include the disclosed cyber security system as a subset. A computeresource, as used herein, may refer to a database, a virtual machine, astorage, a keystore, a scanning system, a load balancer, a server, acomputer, a container, or any physical or virtual component integratedin or communicatively connected to a cloud infrastructure. By way ofexample, the compute resource may be scanning system 101, any ofdatabases 103A-103D, any of virtual machines 107A-107D, any of databases109A-109D, any of storage 111A-111D, any of keystores 113A-113D, or loadbalancer 115 in cloud infrastructure 106 in FIG. 1.

A key to access a compute resource, as used herein, may refer tocomputerized data that includes a credential for granting permission toan accessor to access the compute resource, or a service or functionprovided by the compute resource. By way of example, the key may includeat least one of a password, a remote access key, a script containing apassword, a cloud key (e.g., a credential file for accessing a cloudservice, such as an AWS credential file), an Secure Shell (SSH) key, anAWS key, a private component of a private-public key pair, or any typeof credential that provide checked or unchecked access to the computeresource. Matching a key to a compute resource, as used herein, mayrefer to confirming, verifying, validating, or any operation or processof determining that the key is valid for an accessor (e.g., anothercompute resource) to access the compute resource. For example, to matcha key to a compute resource, an accessor may test by using the key toaccess the compute resource and determines that the key is matched tothe compute resource if such access is successful. As another example,to match a key to a compute resource, an accessor may perform methods oralgorithms to verify that the key is matched to the compute resourcewithout using the key to access the compute resource.

Consistent with disclosed embodiments, at least one processor may beconfigured to analyze a cloud environment to identify a plurality ofkeys to the compute resources in the cloud environment. In someembodiments, the at least one processor may analyze the cloudenvironment to identify the plurality of keys to the compute resourcesin the cloud environment in any of steps 231, 237, or 239 in FIG. 2D. Insome embodiments, the at least one processor may analyze the cloudenvironment to identify the plurality of keys to the compute resourcesin the cloud environment in any step described in association with FIGS.2A-2D. In some embodiments, at least one of the plurality of keys mayinclude at least one of a password (e.g., a combination of alphanumericcharacters and symbols), a script (e.g., a PYTHON® script or a shellscript) containing a password, a cloud key, or an Secure Shell (SSH)key. For example, a cloud key may be a key for accessing a cloudresource.

A cloud environment, as used herein, may refer to a computingenvironment running on a cloud. By way of example, the cloud environmentmay include or be part of cloud infrastructure 106 in FIG. 1. Analyzinga cloud environment, as used herein, may refer to an operation or aprocess of separating or dividing the cloud environment into parts orcomponents (e.g., physical components or logic components), thendetermining nature and relationship of the parts or components based ondata associated with the parts or components.

By way of example, if the cloud environment is cloud infrastructure 106in FIG. 1, to analyze cloud infrastructure 106, the at least oneprocessor may access cloud infrastructure 106 (e.g., via network 105 orvia internal connections in cloud infrastructure 106) and obtain a listof compute resources in cloud infrastructure 106 (e.g., scanning system101, any of databases 103A-103D, any of virtual machines 107A-107D, anyof databases 109A-109D, any of storage 111A-111D, any of keystores113A-113D, or load balancer 115). For example, the at least oneprocessor may obtain the list of compute resources by reading aconfiguration file from a database (e.g., one of databases 109A-109D),or visit available compute resources one after another throughcommunicative connections between the compute resources to generate thelist of compute resources. After obtaining the list of compute resourcesin cloud infrastructure 106, the at least one processor may determinethe nature of the compute resources, such as their types, numbers,functions, or any other characteristics or features. The at least oneprocessor may further determine the relationship between the computeresources, such as communicative connections, access privileges, datainput/output directions, or controls between the compute resources.

Identifying a key to a compute resource, as used herein, may refer to anoperation or a process of locating, recognizing, or any operation orprocess or analyzing computerized data or information to determine thatthe computerized data or information is a key to the compute resources.By way of example, the at least one processor may analyze cloudinfrastructure 106 in FIG. 1 to recognize a list of compute resources incloud infrastructure 106 (e.g., scanning system 101, any of databases103A-103D, any of virtual machines 107A-107D, any of databases109A-109D, any of storage 111A-111D, any of keystores 113A-113D, or loadbalancer 115). Then, the at least one processor may read computerizeddata stored in a compute resource and identify that some of thecomputerized data are one or more keys to other compute resources incloud infrastructure 106. For example, to recognize the keys, the atleast one processor may read and compare the computerized data withrecords stored in keystores 113A-113D, and determine that thecomputerized data is a key if it matches a record in any of keystores113A-113D. As another example, the at least one processor may read thecomputerized data and check its syntaxes, text string patterns, fileformats, file properties, encryption manners, library versions, softwareversions, or any other characteristics or features of the computerizeddata, and determine that the computerized data is a key if its checkedcharacteristics or features fit a predetermined pattern of a key or fitan entry in a dictionary of keys. For example, the dictionary of keysmay be stored in a keystore (e.g., any of keystores 113A-113D).

In some embodiments, the plurality of keys may be stored in at least oneworkload. A workload, for example, may refer to a specific application,service, capability, or a specific amount of work that can be run on acloud resource, system, or infrastructure. By way of example, a workloadmay be a virtual machine, a database server, a container, a Hadoop node,an application, a storage server, a load balancer, or an IAM (Identityand Access Management) configuration. By way of example, with referenceto FIG. 1, cloud infrastructure 106 may include workloads such asscanning system 101, databases 103A-103D, virtual machines 107A-107D,databases 109A-109D, storage 111A-111D, keystores 113A-113D, and loadbalancer 115.

Consistent with disclosed embodiments, at least one processor may beconfigured to perform a cryptographic analysis on the plurality of keysto identify a first set of fingerprints that uniquely identify each ofthe plurality of keys. The first set of fingerprints may benon-functional. In some embodiments, the at least one processor mayperform the cryptographic analysis in step 237 of FIG. 2D. In someembodiments, the at least one processor may perform the cryptographicanalysis in any step described in association with FIGS. 2A-2D.

A cryptographic analysis on data, as used herein, may refer to anoperation or process of identifying ciphertext, ciphers andcryptosystems contained in the data to discover hidden aspects of thedata that may improve or weaken security of the data or computeresources associated with the data. In some embodiments, to perform thecryptographic analysis on the plurality of keys, the at least oneprocessor may perform an algorithm on the plurality of keys to convertthe plurality of keys into another form of data. For example, the atleast one processor may perform a hashing process on the plurality ofkeys (e.g., by inputting values of the keys to a hash function) toobtain corresponding hash values of respective keys.

A fingerprint of a key, as used herein, may refer to non-functional data(e.g., a numeric value, an alphanumeric string, or any combination ofletters, numbers, or symbols) generated based on the key and mayuniquely identify the key. By way of example, a fingerprint may begenerated by performing a hashing process on a key or a part of the key.The hashing process may include, for example, an MD5 algorithm, an SHA-1algorithm, an SHA-2 algorithm, an SHA-3 algorithm, a RIPEMD-160algorithm, a BLAKE2 algorithm, a BLAKE3 algorithm, or any type ofcryptographic hash algorithms. In such cases, the fingerprint may be ahash value of the key, a part (e.g., a truncated part) of the hash valueof the key, a hash value of a part of the key, or a part (e.g., atruncated part) of the hash value of the part of the key. The hash valuemay be unique (e.g., non-overlap with any hash value of any other key)and non-functional (e.g., unable to be used as a key to access a computeresource). To identify the first set of fingerprints, the at least oneprocessor may perform the hashing process on the plurality of keys toobtain a plurality of hash values, and search the cloud environment tocheck whether there exists any compute resource that stores theplurality of hash values.

In some embodiments, at least one of the first set of fingerprints maybe non-identical to any key of the plurality of keys. For example, ifthe first set of fingerprints are hash values, they may be non-identicalto the plurality of keys.

Consistent with disclosed embodiments, at least one processor may beconfigured to analyze trust configurations of the compute resources toidentify a second set of fingerprints for each of the compute resources.In some embodiments, the at least one processor may analyze the trustconfigurations in step 233 of FIG. 2D. In some embodiments, the at leastone processor may analyze the trust configurations in any step describedin association with FIGS. 2A-2D.

A trust configuration, as used herein, may refer to data (e.g., a storedfile, a database entry, a value stored in a data structure, or anycomputerized information) that stores a pre-established trustrelationship between at least two compute resources. For example, atrust configuration may be a file storing a trust policy (e.g., a publickey infrastructure (PKI), a digital signature system, or an AWS trustpolicy). Analyzing a trust configuration, as used herein, may refer toan operation or a process of separating or dividing compute resourcesassociated with the trust configuration into units or groups, thendetermining nature and relationship of the units or groups based onrelationship data associated with the units or groups. For example, therelationship data may include flags, indicators, or any type of valuethat indicates a first compute resource has an access privilege to asecond compute resource.

A fingerprint for a compute resource, as used herein, may refer tonon-functional data (e.g., a numeric value, an alphanumeric string, orany combination of letters, numbers, or symbols) generated based on akey for accessing the compute resource and may uniquely identify thekey. By way of example, a fingerprint for a compute resource may begenerated by applying a cryptographic hash function (e.g., an SHA-1 orSHA-2 function) to a key for accessing the compute resource to obtain asequence of bytes (e.g., a hash value or a modified hash value), and thesequence of bytes may be the fingerprint for the compute resource. Thekey may be uniquely associated with the compute resource.

For example, to identify the second set of fingerprints, the at leastone processor may analyze a trust configuration file (e.g., a filestoring fingerprints and their associated data) by reading the bytestream of the trust configuration file to determine whether any sequenceof bytes that fits to a predetermined pattern (e.g., an alphanumericstring pattern). The sequences of bytes that fit to the predeterminedpattern may be determined as the second set of fingerprints.

Consistent with disclosed embodiments, at least one processor may beconfigured to compare the first set of fingerprints with the second setof fingerprints to match keys with the compute resources without usingthe keys to access the compute resources. In some embodiments, the atleast one processor may compare the first set of fingerprints with thesecond set of fingerprints in any step described in association withFIGS. 2A-2D. Comparing a first fingerprint and a second fingerprint, asused herein, may refer to performing a textual, numerical, or semanticcomparison of the first fingerprint and the second fingerprint, orperforming an algorithmic conversion of at least one of the firstfingerprint or the second fingerprint to further perform a textual,numerical, or semantic comparison of the conversion results. By way ofexample, a first compute resource may store a key (e.g., a public key)for accessing a second compute resource. The at least one processor mayanalyze the cloud environment to identify the key from the first computeresource, then may perform the cryptographic analysis described hereinto identify a first fingerprint of the key. A third compute resource(e.g., may be the same as or different from the second compute resource)may store in its trust configurations a second fingerprint of the key.The second fingerprint may be generated by a different processor at adifferent time. The at least one processor may then analyze the trustconfigurations of the third compute resource to identify the secondfingerprint. The at least one processor may then compare the firstfingerprint and the second fingerprint to determine whether they matcheach other. If the first fingerprint matches with the secondfingerprint, the at least one processor may determine that the keyidentified from the first compute resource is a key for accessing thesecond compute resource. As can be seen, after comparison, if the firstset of fingerprints are matched with the second set of fingerprints,keys may be matched with the compute resources, and the at least oneprocessor needs not use the keys to access the compute resources toconfirm that the keys are matched to the compute resources.

Consistent with disclosed embodiments, the at least one processor mayfurther analyze a multi-machine interaction in the cloud environmentusing the first set of fingerprints. A multi-machine interaction, asused herein, may refer to data input/output, operation control, statuspolling, scanning, or any type of an interaction between a plurality ofmachines in a cloud environment. Analyzing a multi-machine interaction,as used herein, may refer to an operation or a process of separating ordividing machines in the cloud environment into units or groups, thendetermining nature and relationship of the units or groups based onrelationship data associated with the units or groups. For example, therelationship data may be the first set of fingerprints.

By way of example, to analyze the multi-machine interaction, the atleast one processor may compare the first set of fingerprints with thesecond set of fingerprints. If a first fingerprint of the first set offingerprints matches with a second fingerprint of the second set offingerprints, the at least one processor may determine that a firstcompute resource associated with the first fingerprint may have aninter-machine interaction (e.g., having an ability to access the other)with a second compute resource associated with the second fingerprint.By way of example, a first compute resource may store a key (e.g., aprivate key) for accessing a second compute resource. The at least oneprocessor may analyze the cloud environment to identify the key from thefirst compute resource, then may perform the cryptographic analysisdescribed herein to identify a first fingerprint of the key. A thirdcompute resource (e.g., may be the same as or different from the secondcompute resource) may store in its trust configurations a secondfingerprint of the key. The at least one processor may then analyze thetrust configurations of the third compute resource to identify thesecond fingerprint. The at least one processor may then compare thefirst fingerprint and the second fingerprint to determine whether theymatch each other (e.g., being the same). If the first fingerprintmatches with the second fingerprint, the at least one processor maydetermine that the key identified from the first compute resource is akey for accessing the second compute resource, and may further determinean inter-machine interaction in which the first compute resource hasability to access the second compute resource.

Consistent with disclosed embodiments, the at least one processor mayfurther analyze a multi-machine interaction in the cloud environmentusing the plurality of keys. For example, the at least one processor mayuse the plurality of keys as the relationship data for determiningnature and relationship of compute resources in the cloud environment.By way of example, to analyze the multi-machine interaction, the atleast one processor may compare a first key for accessing a first one ofthe compute resources and a second key for accessing a second one of thecompute resources. If the first key matches with (e.g., is identical to)the second key, the at least one processor may determine that the firstone of the compute resources may have an interaction (e.g., having anability to access the other) with the second one of the computeresources.

By way of example, FIG. 9 is a block diagram illustrating an exemplaryprocess 900 of matching keys with compute resources in a cloudenvironment, consistent with the disclosed embodiments. While the blockdiagram may be described below in connection with certain implementationembodiments presented in other figures, those implementations areprovided for illustrative purposes only, and are not intended to serveas a limitation on the block diagram. For example, the steps in FIG. 9may be executed in any order, steps may be duplicated, or steps may beomitted. In some embodiments, the process 900 may be performed by atleast one processor (e.g., a CPU) of a computing device or system (e.g.,scanning system 101 in FIG. 1) to perform operations or functionsdescribed herein, and may be described hereinafter with reference toFIGS. 1-2D by way of example. In some embodiments, some aspects of theprocess 900 may be implemented as software (e.g., program codes orinstructions) that are stored in a memory or a non-transitorycomputer-readable medium. In some embodiments, some aspects of theprocess 300 may be implemented as hardware (e.g., a specific-purposecircuit). In some embodiments, the process 300 may be implemented as acombination of software and hardware.

FIG. 9 includes process blocks 902-908. At block 902, at least oneprocessor may analyze a cloud environment to identify a plurality ofkeys to the compute resources in the cloud environment. In someembodiments, the plurality of keys may be stored in at least oneworkload. In some embodiments, at least one of the plurality of keys mayinclude at least one of a password (e.g., a combination of alphanumericcharacters and symbols), a script (e.g., a PYTHON® script or a shellscript) containing a password, a cloud key, or an Secure Shell (SSH)key.

At block 904, the at least one processor may perform a cryptographicanalysis on the plurality of keys to identify a first set offingerprints that uniquely identify each of the plurality of keys. Thefirst set of fingerprints may, in some embodiments, be non-functional.In some embodiments, at least one of the first set of fingerprints maybe non-identical to the key.

At block 906, the at least one processor may analyze trustconfigurations of the compute resources to identify a second set offingerprints for each of the compute resources. As discussed above, toidentify the second set of fingerprints, in some embodiments, the atleast one processor may analyze a trust configuration file (e.g., a filestoring fingerprints and their associated compute resources) by readingthe byte stream of the trust configuration file to determine whether anysequence of bytes that fits to a predetermined pattern (e.g., analphanumeric string pattern). The sequences of bytes that fit to thepredetermined pattern may be determined as the second set offingerprints.

At block 908, the at least one processor may compare the first set offingerprints with the second set of fingerprints to match keys with thecompute resources without using the keys to access the computeresources. As discussed above, in some embodiments, a first computeresource may store a key (e.g., a private component of a private-publickey pair) to a second compute resource, and the second compute resourcemay store in its trust configurations a second fingerprint of the key.The at least one processor may analyze the cloud environment to identifythe key from the first compute resource, then may perform thecryptographic analysis described herein to identify a first fingerprintof the key. The at least one processor may then analyze the trustconfigurations of the second compute resource to identify the secondfingerprint. The at least one processor may then compare the firstfingerprint and the second fingerprint to determine whether they matcheach other (e.g., being identical). If the first fingerprint matcheswith the second fingerprint, the at least one processor may determinethat the key identified from the first compute resource is a key foraccessing the second compute resource.

Consistent with disclosed embodiments, besides blocks 902-908, the atleast one processor may further analyze a multi-machine interaction inthe cloud environment using the first set of fingerprints. By way ofexample, to analyze the multi-machine interaction, the at least oneprocessor may compare the first set of fingerprints with the second setof fingerprints. As discussed above, in some embodiments, a firstcompute resource may store a key (e.g., a private key) for accessing asecond compute resource. The at least one processor may analyze thecloud environment to identify the private component from the firstcompute resource, then may perform the cryptographic analysis describedherein to identify a first fingerprint of the key. A third computeresource (e.g., may be the same as or different from the second computeresource) may store in its trust configurations a second fingerprint ofthe key. The at least one processor may then analyze the trustconfigurations of the third compute resource to identify the secondfingerprint. The at least one processor may then compare the firstfingerprint and the second fingerprint to determine whether they matcheach other (e.g., being the same). If the first fingerprint matches withthe second fingerprint, the at least one processor may determine thatthe key identified from the first compute resource is a key foraccessing the second compute resource, and may further determine aninter-machine interaction in which the first compute resource hasability to access the second compute resource.

Consistent with disclosed embodiments, besides blocks 902-908, the atleast one processor may further analyze a multi-machine interaction inthe cloud environment using the plurality of keys. By way of example, toanalyze the multi-machine interaction, the at least one processor maycompare a first key for accessing a first one of the compute resourcesand a second key for accessing a second one of the compute resources.

Hybrid Ephemeral Scanner Techniques

Aspects of this disclosure may include accessing a primary accountmaintained in a cloud environment. A primary account as used herein, mayrefer to a principal or main identity created for a person in a computeror computing system. A primary account may also be created for machineentities, such as service accounts for running programs, system accountsfor storing system files and processes, and root and administratoraccounts for system administration. A cloud environment, as used herein,may refer to a platform implemented on, hosted on, and/or accessingservers that are accessed over the Internet. An example of a cloudenvironment is cloud infrastructure 106 in FIG. 1. In some embodiments,scanning system 101 of FIG. 1 may gain access to an account within cloudinfrastructure 106.

Aspects of this disclosure may include receiving information defining astructure of the primary account, wherein the structure includes aplurality of assets.

Information as used herein, may refer to data received. Structure of theprimary account as used herein, may refer to a set up or of the primaryaccount. A plurality of assets as used herein, may refer to one or moredata, devices, or components within an organization's system. Forexample, the plurality of assets may include any of virtual machines107A-107D, databases 109A-109D, storage 111A-111D, keystores 113A-113D,load balancer 115, log files or databases, API gateway resources, APIgateway REST APIs, Autoscaling groups, CloudTrail logs, CloudFrontservices, volumes, snapshots, VPCs, subnets, route tables, network ACLs,VPC endpoints, NAT gateways, ELB and ALB, ECR repositories, ECSclusters, services, and tasks, EKS, S3 bucket and Glacier storage, SNStopics, IAM roles, policies, groups, users, KMS keys, and Lambdafunctions.

In some embodiments, scanning system 101 of FIG. 1 may receiveinformation relating to the structure of an account. In such anembodiment, the structure of the account may include virtual machines107A-D and databases 109A-109D, for example. In some embodiments, theinformation may be acquired from another device, received via a one waycommunication, received in response to a request, retrieved from astorage device, or generated.

In some embodiments, the information may exclude raw data of the primaryaccount. Raw data as used herein, may refer to a collection of data asgathered before it has been processed, cleaned, or analyzed. Forexample, raw data may include usage data, passwords, and cache.

Aspects of this disclosure may include deploying, inside the primaryaccount, at least one ephemeral scanner configured to scan at least oneblock storage volume and to output metadata defining the at least oneblock storage volume. In some embodiments, the output may exclude rawdata of the primary account. In some embodiments, the ephemeral scannermay be deployed inside a secondary account for which trust has beenestablished with a primary account. For example, a secondary account onanother system may have an existing trust relationship (such as a cloudtrust policy) with a first account. The ephemeral scanner may beoperated inside of that secondary account to scan block storageassociated with the first account. Each account may be hosted on thesame system or on different systems.

Further, in some embodiments, the at least one ephemeral scanner may beconfigured to periodically scan at least one block storage volume. Forexample, the scanner may be configured to scan at least one blockstorage volume once per hour, once per day, once per week, or more orless often.

Further, in some embodiments, the at least one ephemeral scanner may beperiodically deployed to scan at least one block storage volume. Forexample, the scanner may be deployed for scanning at least one blockstorage volume once per hour, once per day, once per week, or more orless often.

Outputting metadata as used herein, may refer to producing a set of datathat describes and gives information about other data. In someembodiments, scanning system 101 of FIG. 1 may scan a block storagevolume and output data related to it (e.g., vulnerability information,configuration information, malware information, risk analysisinformation, and sensitive information). Periodically scanning as usedherein, may refer to conducting a scan occurring or recurring at regularintervals. In some embodiments, the ephemeral scanner is configured toperform vulnerability scanning of the at least one block storage volume.In such an embodiment the ephemeral scanner may scan the block storagevolume to check for security vulnerabilities on the device. In someembodiments, the ephemeral scanner is configured to performconfiguration scanning of the at least one block storage volume. In suchan embodiment the ephemeral scanner may scan the block storage volume tocheck for configuration information related to the device. In someembodiments, the ephemeral scanner may scan the block storage volume inorder to look for security issues. In some embodiments, the ephemeralscanner is configured to perform malware scanning of the at least oneblock storage volume. In such an embodiment the ephemeral scanner mayscan the block storage volume to check for malware information relatedto the device. As discussed above with respect to FIG. 2D, in step 235,scanning system 101 may perform a step of malware scanning. In someembodiments, scanning system 101 may perform malware scanning across allfilesystems in the snapshot (e.g., gathered from virtual machines107A-107D or storage 111A-111D). Scanning system 101 may use multiplemalware scanning software solutions to perform a malware scan againstthe filesystems, including one sourced from another vendor, such asbucketAV, Trend Micro Cloud One, Sophos Cloud Optix, Crowdstrike FalconCWP, or others. In some embodiments, malware scanning in step 235comprises utilizing signatures, heuristics, or sandboxing capabilitiesto deduce whether there is an infection on the machine.

In some embodiments, the ephemeral scanner is configured to performlateral-movement risk analysis of the at least one block storage volume.In such an embodiment the ephemeral scanner may scan the block storagevolume to check for lateral-movement risk information related to thedevice. For example, in some embodiments, scanning system 101 mayperform a “backward” analysis of the specific asset to identify exposurerisk to assets downstream of the specific asset, wherein the downstreamexposure risk includes an identification of an exposed asset, an entrypoint to the exposed asset, and lateral movement risks associated withthe exposed asset.

Further, as discussed above with respect to FIG. 2D, in step 237,scanning system 101 may perform a step of lateral movement scanning. Anattacker who establishes a network foothold usually attempts to movelaterally from one resource to another in search of rich targets such asvaluable data. Stolen passwords and keys unlock access to servers,files, and privileged accounts. In some embodiments, scanning system 101may gather keys from each scanned system or device (e.g., virtualmachines 107A-107D or storage 111A-111D). In some embodiments, scanningsystem 101 searches for passwords, scripts, shell history, repositories,or other data that may contain passwords, cloud access keys, SSH keys,or other key/password/access information that provide unchecked accessto important resources. In some embodiments, scanning system 101searches for such keys/passwords/access information and calculates a“hash” (a mathematical fingerprint) of each string. Scanning system 101then attempts to match the hashed strings to hashes of strings that thatare stored on different systems or devices. This will be used to detectthe potential lateral movement between assets.

In some embodiments, the ephemeral scanner is configured to performsensitive information scanning of the at least one block storage volume.In such an embodiment the ephemeral scanner may scan the block storagevolume to check for sensitive information related to the device. Asdiscussed above with respect to FIG. 2D, in step 241, scanning system101 may perform a step of sensitive information scanning. In someembodiments, scanning system 101 may search the snapshot for sensitiveinformation, such as personally identifiable information (PII), SocialSecurity numbers, healthcare information, or credit card numbers. Insome embodiments, scanning system 101 may search data repository historyas well. This is because it is not uncommon for an entire productionenvironment repository to be cloned, with no one remembering the copycontains sensitive information. In some situations, detecting sensitivedata not secured is critical in adherence to data privacy regulations.

In some embodiments, the ephemeral scanner is configured to performcontainer scanning of the at least one block storage volume. In such anembodiment the ephemeral scanner may scan the block storage volume tocheck for container information related to the device. As discussed withrespect to FIG. 2D, in step 243, scanning system 101 may perform a stepof container scanning. In some embodiments, scanning system 101 mayapply one or more of the preceding steps of FIG. 2D againstcontainerized environments. In some embodiments, in order to do so,scanning system 101 reconstructs a container runtime layered file system(LFS) before recursively running one or more of steps 231-241 on thereconstructed file system.

In some embodiments, the ephemeral scanner is configured to perform keysand password scanning of the at least one block storage volume. In suchan embodiment the ephemeral scanner may scan the block storage volume tocheck for keys and password information related to the device. Asdiscussed above with respect to FIG. 2D, in step 239, scanning system101 may perform a step of key/password scanning. As one examplesituation, suppose there is a weak or unprotected password stored (inplain text) in storage 111A. For example, if a personal email accounthas been compromised, the passwords may be known about in advance.Scanning system 101 may search the snapshot for similar usernames orlogin names, and, either using known dictionaries or the account owner'spreviously leaked passwords (stored in, e.g., database 103A), mayattempt to login to one or more systems or devices in cloudinfrastructure 106, and may record the result thereof.

In some embodiments, defining the at least one block storage volumeincludes presenting risk data without sharing consumer data or data thatwas used to identify the risk data. Risk data as used herein, may referto information relating to causing harm. Consumer data as used herein,may refer to a user's personal information or any information trailuser's leave behind as a result of their computer or Internet use. Dataused to identify the risk as used herein, may refer to information fordetermining possible issues. In some embodiments, scanning system 101 ofFIG. 1 may present information without sharing a user's personalinformation or any information trail user's leave behind as a result oftheir computer or Internet use.

In some embodiments, the metadata defining the at least one blockstorage volume includes at least one of: an indication of an installedapplication, a version of an installed application, an operating systemconfiguration, an application configuration, or a profile configuration.An indication of an installed application as used herein, may refer to asign or signal of a stored program. A version of an installedapplication as used herein, may refer to an older or newer form of astored program. An operating system configuration as used herein, mayrefer to one or more computer system settings that have been set bydefault automatically or manually by a given program or the user. Anapplication configuration as used herein, may refer to one or morecomputer program settings that have been set by default automatically ormanually by a given program or the user. A profile configuration as usedherein, may refer to one or more computer program file settings thathave been set by default automatically or manually by a given program orthe user.

Aspects of this disclosure may include receiving a transmission of themetadata from the at least one ephemeral scanner. In some embodiments,the transmission may exclude raw data of the primary account. Atransmission of metadata as used herein, may refer to movement of a setof data that describes and gives information about other data. In someembodiments, scanning system 101 of FIG. 1 may receive data excludingany raw data (e.g., data as gathered before it has been processed,cleaned or analyzed).

Aspects of this disclosure may include analyzing the received metadatato identify a plurality of cybersecurity vulnerabilities. A plurality ofcybersecurity vulnerabilities as used herein, may refer to a weakness ina system. For example, a cybersecurity vulnerability may be exploited bycybercriminals to gain unauthorized access to a computer system. In someembodiments, scanning system 101 of FIG. 1 may analyze the received datain order to identify any weakness in a system (e.g., to avoidcybercriminals gaining unauthorized access to a computer system). Insome embodiments, vulnerability information may include informationstored in a system.

Aspects of this disclosure may include correlating each of theidentified plurality of cybersecurity vulnerabilities with one of theplurality of assets. In some embodiments, scanning system 101 of FIG. 1may connect a security risk with an asset in the cloud environment. Insuch embodiments, the connection or correlation of vulnerability toasset may allow the system to address the vulnerability.

Aspects of this disclosure may include generating a report correlatingthe plurality of cybersecurity vulnerabilities with the plurality ofassets. A report as used herein, may refer to a document containinginformation. For example, a report may notify the administrator of awebsite or application about a problem such as a security issue orvulnerability in the system that should be addressed. In someembodiments, scanning system 101 of FIG. 1 may create a report providinginformation related to the vulnerability and asset. In such anembodiment, the report may allow for the vulnerability to be addressedand resolved.

In such embodiments, the system may allow scanners (e.g., ephemeralscanners, scanning system 101) to run inside an account, including anAmazon Web Services, Azure, or GCP account. In this mode, a cloudcybersecurity service may generate ephemeral scanners inside an accountthat performs the same actions as a SAAS node but are logically hostedinside the account.

In some embodiments, the at least one processor is further configured toreceive a transmission of updated metadata defining the at least oneblock storage volume in response to at least one change to the at leastone block storage volumes. Updated metadata as used herein, may refer toa renewed set of data that describes and gives information about otherdata.

FIG. 10 is a block diagram of a method 1000 for deployment of ephemeralscanners, consistent with disclosed embodiments. In some embodiments,the method may include seven (or more or less) steps:

Block 1002: Access a primary account maintained in a cloud environment.In some embodiments, scanning system 101 of FIG. 1 may gain access to anaccount within cloud infrastructure 106 using a password stored in adatabase, for example.

Block 1004: Receiving information defining a structure of the primaryaccount, wherein the structure includes a plurality of assets. In someembodiments, the information may exclude raw data of the primaryaccount. In some embodiments, scanning system 101 of FIG. 1 may receivedata relating to the structure of an account. In such an embodiment, thestructure of the account may include virtual machines 107A-D anddatabases 109A-109D, for example.

Block 1006: Deploying, inside the primary account, at least oneephemeral scanner configured to periodically scan at least one blockstorage volume and to output metadata defining the at least one blockstorage volume. In some embodiments, the output may exclude raw data ofthe primary account. In some embodiments, scanning system 101 of FIG. 1may scan a block storage volume and output data related to it (e.g.,vulnerability information, configuration information, malwareinformation, risk analysis information, and sensitive information).

Block 1008: Receiving a transmission of the metadata from the at leastone ephemeral scanner. In some embodiments, the transmission may excluderaw data of the primary account. In some embodiments, scanning system101 of FIG. 1 may receive data excluding any raw data (e.g., data asgathered before it has been processed, cleaned or analyzed).

Block 1010: Analyzing the received metadata to identify a plurality ofcybersecurity vulnerabilities. For example, a cybersecurityvulnerability may be exploited by cybercriminals to gain unauthorizedaccess to a computer system. In some embodiments, scanning system 101 ofFIG. 1 may analyze the received data in order to identify any weaknessin a system (e.g., to avoid cybercriminals gaining unauthorized accessto a computer system).

Block 1012: Correlating each of the identified plurality ofcybersecurity vulnerabilities with one of the plurality of assets. Insome embodiments, scanning system 101 of FIG. 1 may connect a securityrisk with an asset in the cloud environment. In such embodiments, theconnection or correlation of vulnerability to asset may allow the systemto address the vulnerability.

Block 1014: Generating a report correlating the plurality ofcybersecurity vulnerabilities with the plurality of assets. For example,a report may notify the administrator of a website or application abouta problem such as a security issue or vulnerability in the system thatshould be addressed. In some embodiments, scanning system 101 of FIG. 1may create a report providing information related to the vulnerabilityand asset. In such an embodiment, the report may allow for thevulnerability to be addressed and resolved.

Risk Information Aggregation Techniques

FIG. 11 represents a schematic block diagram 1100 illustrating anexemplary embodiment of a method for providing a dashboard aggregatingrisk information.

Assets operating in a cloud environment face myriad cybersecurity risksthat vary in type and nature of threat with increasing regularity. Inorder to combine the varied and multiple cybersecurity risks an assetmay encounter in a cloud environment into a single view to allow forfaster and more flexible processing, prioritization and mitigation, asystem and method of aggregating cybersecurity risks into a singledashboard is needed. Aggregation of multiple cybersecurity risks into asingle view for an administrator is needed. In one of many embodiments,an exemplary embodiment may include a graphical user interface systemfor providing comprehensive cloud environment risk inventoryvisualization. A graphical user interface system may include systemssimilar in appearance and functionality to Microsoft Windows, Mac OS,Ubuntu Unity, Gnome Shell, Android, Apple iOS, Blackberry OS, Windows 10Mobile, PalmOS-Web OS, or Firefox OS. For example, cloud infrastructure106 may be the cloud environment consisting of virtual machines107A-107D, databases 109A-109D, storage 111A-111D, keystores 113A-113D,and load balancer 115, and the cloud-based storage volume may becontained in storage 111A-111D. The cloud environment may includeservice provided by a third party such as Amazon Web Services, MicrosoftAzure, Google Cloud, Alibaba Cloud, IBM Cloud, Oracle, Salesforce, SAP,or similar service. Visualizations provided by the above system mayinclude graphical, sequential, or multi-dimensional displays of riskinventories. For example, cloud infrastructure 106 may be the cloudenvironment consisting of virtual machines 107A-107D, databases109A-109D, storage 111A-111D, keystores 113A-113D, and load balancer115, and the cloud-based storage volume may be contained in storage111A-111D.

An exemplary embodiment may also include at least one processor. The atleast one processor may be part of a personal computer, tablet,smartphone, or virtual machine for processing threats andvulnerabilities to a cloud-based storage volume. A processor may includeone or more integrated circuits (IC), including application-specificintegrated circuit (ASIC), microchips, microcontrollers,microprocessors, all or part of a central processing unit (CPU),graphics processing unit (GPU), digital signal processor (DSP),field-programmable gate array (FPGA), server, virtual server, or othercircuits suitable for executing instructions or performing logicoperations.

In an embodiment may include a processor configured to cause a displayto present a plurality of asset categories (step 1101). A display may begraphical, sequential, or multi-dimensional. A plurality may include atleast one asset category to be displayed. Asset categories may includeat least one of an account category, a container category, a databasecategory, an image category, a container category, a managed servicecategory, a messaging service category, a monitoring category, a networkcategory, a storage category, a user category, a access category, avirtual machine category, or a serverless category.

An account category may further include listing of assets based on typeof account associated with that user. A type of account may includeactive user account, passive user account, administrator account,maintainer account, a system account, superuser account, or a guest useraccount.

A container category may include one or more containers currently listedin the system. A container may involve specific versions of programminglanguage runtimes, libraries required to run software, or another methodof packaging applications abstracted from the cloud environment.

A database category may include one or more databases managed andmaintained in relation to the system. Databases may include a NoSQLdatabase, a relational database, a cloud database, a columnar database,a wide column database, a key-value database, an object-orienteddatabase, a hierarchical database, or any other kind of database.Databases may be implemented using ElasticCache, ElasticSearch,DocumentDb, DynamoDB, Neptune, RDS, Aurora, Redshift clusters, Kafkaclusters, or EC2 instances.

An image category may contain one or more images based on image type,size, and content. Images may include images of one or more virtualmachines.

A managed service category may include one or more managed serviceslisted in the above system, to include at least client or customer-ownedsystems being managed by a third party entity.

A messaging service category may include systems/programs communicatingwith other systems/programs using services such as Google Cloud Pub andSub communications, AWS SQS, or similar queues found in InformationSystems.

A monitoring category may include centralized or decentralized methodsof security monitoring systems.

A network category may include one or more systems of establishing aform of communicative connectivity between systems, e.g., TCP-IPservices.

A storage category may list one or more methods of data storage, toinclude Direct Attached Storage, Network Attached Storage, SSD FlashDrive Arrays, Hybrid Flash Arrays, Hybrid Cloud Storage, BackupSoftware, Backup Appliances, Cloud Storage, or similar. Storage mayinclude data structures, instructions, or any other data to be containedin a storage medium.

A user category may include one or more users of a given system alongwith identifying information relating to its unique or semi-uniqueidentifier, level of authorized access and permissions, and storagevolumes accessible by said user.

An access category may include one or more levels of access permissionand a listing of users or devices granted access at a given level ofaccess permission to a system.

A virtual machine category may list one or more virtual machinesaccessible to a system and the levels and types of access granted to agiven virtual machine.

A serverless category may list one or more storage volumes stored on aserverless computing system such as Kubeless, Fission, Google AppEngine, AWS Lambda, Google Cloud Functions, IBM Cloud Function, IBMCloud Code Engine, Microsoft Azure Functions, Cloudflare Workers, andCompute@Edge.

In an embodiment, an exemplar may include a processor configured toreceive, via an input device, a selection of a particular asset category(step 1103). An input device may include a personal computer, tablet,smartphone, or virtual machine. A processor may include one or moreintegrated circuits (IC), including application-specific integratedcircuit (ASIC), microchips, microcontrollers, microprocessors, all orpart of a central processing unit (CPU), graphics processing unit (GPU),digital signal processor (DSP), field-programmable gate array (FPGA),server, virtual server, or other circuits suitable for executinginstructions or performing logic operations. A selection of one or moreasset categories may be received and updated as new visualizations aredeveloped based on the current threats to an asset in that category.Asset categories may be selected or deselected by an end user. Once aparticular asset category is selected, it may be added to a list ofselected asset categories with a list for deselected categories as well.The list of selected asset categories may organized per category or maybe compiled to include all current threats in a comprehensive selectedasset threat list.

One exemplary embodiment may further include a processor configured tocause the display to present a list of assets in the selected categorythat have cyber security risks (step 1105). When an asset in a selectedcategory has a cyber security risk associated with it, the asset mayappear in a list of all listed categories having a cyber security riskassociated with it, and may be organized by individual category, type ofcyber security risk, or some combination or sequential ordering methodsbased on the information available to the processor and its end user.

In one of many exemplary embodiments a processor may be configured toretrieve workload component cybersecurity risk information (step 1107A)for each listed asset. When a category of assets is selected, aprocessor may be configured to order those assets according to availablecybersecurity risk information available to said processor, and mayorganize by type of risk, type of asset, or similar type ofsequentialization. Cybersecurity risk information may be determined fromhistorical threats to the workload component, the current activecybersecurity threats to workload components of certain types, or somecombination of the same.

In an embodiment, a processor may be configured to retrieve cloudcomponent cybersecurity risk information (step 1107B) for each listedasset. Cloud component cybersecurity risk information may includeidentification of the risk based on a semi-unique identifier, the natureof the risk, the likelihood of the risk, or the severity of the risk toeach listed asset. Cybersecurity risk information to a cloud componentmay be determined from historical threats within the cloud environment106, current active cybersecurity threats to similar workload componentsin the cloud environment 106 or the level of risk to assets within thecloud environment 106, as outlined below.

An exemplary embodiment may include a system configured to cause thedisplay to present a common interface (step 1109) providing access tothe workload component cybersecurity risk information and cloudcomponent cybersecurity risk information. The common interface may beconfigured to access component cybersecurity risk information based onthe nature of the risk, the likelihood of the risk, or the severity ofthe risk to the component, including recursive risk—risk that can happenfrom an attacker getting access to a system and using it as a mean toreach other system. On the same interface, a different interface, or asimilar and related interface, a display may present cloud componentcybersecurity risk information based on a semi-unique identifier, thenature of the risk, the likelihood of the risk, or the severity of therisk to each listed asset.

As an exemplary embodiment, the system may be configured to cause thedisplay to present, in the common interface, an interconnection betweenthe workload component cybersecurity risk information and the cloudcomponent cybersecurity risk information (step 1111). With this displaypresented, an exemplary embodiment may allow for a user to prioritizedata from additional sources. The interconnection between workloadcomponent cybersecurity risk information and cloud componentcybersecurity risk information may generate an interface between themand may be presented as an interconnection between them. The commoninterface presented may include direct interconnections between thecomponent cybersecurity risk information and the cloud componentcybersecurity risk information or links from one set of cybersecurityrisk information. For instance, the component cybersecurity riskinformation may include a link to access the cloud componentcybersecurity risk information. Conversely, the cloud componentcybersecurity risk information may include a link to access thecomponent cybersecurity risk information.

In one embodiment, a system may be configured to provide the pluralityof asset categories include at least one of an account category, acontainer category, a database category, an image category, a containercategory, a managed service category, a messaging service category, amonitoring category, a network category, a storage category, a usercategory, a access category, a virtual machine category, or a serverlesscategory. A category may list the currently identified entities of thatcategory type as described below. An account category may include one ormore listed accounts of users of the system. An account category mayfurther include listing of assets based on type of account associatedwith that user. A type of account may include active user account,passive user account, administrator account, maintainer account, asystem account, superuser account, or a guest user account.

A container category may include one or more containers currently listedin the system. A container may involve specific versions of programminglanguage runtimes, libraries required to run software, or another methodof packaging applications abstracted from the cloud environment.

A database category may include one or more databases managed andmaintained in relation to the system. Databases may include a NoSQLdatabase, a relational database, a cloud database, a columnar database,a wide column database, a key-value database, an object-orienteddatabase, a hierarchical database, or any other kind of database.Databases may be implemented using ElasticCache, ElasticSearch,DocumentDb, DynamoDB, Neptune, RDS, Aurora, Redshift clusters, Kafkaclusters, or EC2 instances.

An image category may contain one or more images based on image type,size, and content. Images may include images of one or more virtualmachines displayed. A managed service category may include one or moremanaged services listed in the above system, to include at least clientor customer-owned systems being managed by a third party entity.

A messaging service category may include services of users communicatingwith at least one other user such as Google Cloud Pub and Subcommunications, AWS SQS, or similar queues found in Information Systems.

A monitoring category may include centralized or decentralized methodsof security monitoring systems.

A network category may include one or more systems of establishing aform of communicative connectivity between systems, e.g., TCP-IPservices.

A storage category may list one or more methods of data storage, toinclude Direct Attached Storage, Network Attached Storage, SSD FlashDrive Arrays, Hybrid Flash Arrays, Hybrid Cloud Storage, BackupSoftware, Backup Appliances, Cloud Storage, or similar. Storage mayinclude data structures, instructions, or any other data to be containedin a storage medium.

A user category may include one or more users of a given system alongwith identifying information relating to its unique or semi-uniqueidentifier, level of authorized access and permissions, and storagevolumes accessible by said user.

An access category may include one or more levels of access permissionand a listing of users or devices granted access at a given level ofaccess permission to a system.

A virtual machine category may list one or more virtual machinesaccessible to a system and the levels and types of access granted to agiven virtual machine.

A serverless category may list one or more storage volumes stored on aserverless computing system such as Kubeless, Fission, Google AppEngine, AWS Lambda, Google Cloud Functions, IBM Cloud Function, IBMCloud Code Engine, Microsoft Azure Functions, Cloudflare Workers, andCompute@Edge.

In one of many exemplary embodiments, a system may further include thecommon interface configured to display information relating to at leastone of an asset type, a risk, a region, or an account. A commoninterface may include the ability to configure and reconfigure the assettype, risk, region, or account to appear in any order and at multipleformats for displaying the information relating to those categories.

In another embodiment, a system may provide the common interfaceconfigured to display description for each listed asset. The display ofa description for each listed asset may be listed vertically orhorizontally. The display may be displayed as written text,representative graphical figures, or similar method of displaying theaforementioned types of information for an asset.

In another embodiment, a system may further provide the common interfaceis configured to display at least one of a vulnerability, an insecureconfiguration, an indication of a presence of malware, a neglectedasset, a data at risk, a lateral movement, or an authentication. Avulnerability may include vulnerability data from a vulnerabilitydatabase such as NVD, WPVulnDB, US-CERT, Node.js Security Working Group,OVAL— Red Hat, Oracle Linux, Debian, Ubuntu, SUSE, Ruby AdvisoryDatabase, JVN, Safety DB(Python), Alpine secdb, PHP Security AdvisoriesDatabase, Amazon ALAS, RustSec Advisory Database, Red Hat SecurityAdvisories, Microsoft MSRC, KB, Debian Security Bug Tracker, Kubernetessecurity announcements, Exploit Database, Drupal security advisories,JPCERT. An insecure configuration may include software flaws ormisconfigurations, non-encrypted files, improper file or directorypermissions, unpatched security flaws in server software, enabled oraccessible administrative and debugging functions, administrativeaccount vulnerabilities, SSL certificates and encryption settings notproperly configured, or a similar misconfiguration. Thesemisconfigurations may be discovered by performing a scan, e.g., mayquery devices and systems capable of routing traffic (e.g., loadbalancer 115, routers, switches, firewalls, and proxies) using an APIprovided through a cloud service provider's system to determine networkconfigurations, and may evaluate them against known problematicconfigurations or other configurations. Malware indicated may includeAdware, Botnets, Cryptojacking, Malvertising, Ransomware, RemoteAdministration Tools (RATs), Rootkits, Spyware, Trojans, Virus Malware,Worm Malware, or similar attack vehicles. A neglected asset may includean asset that has been improperly maintained, patched, or similarcybersecurity security measure. A data at risk may include any packet ofdata that may be exposed to a cybersecurity threat. A lateral movementmay include any pathway between assets where a cybersecurity risk cantravel from one affected asset to another affected asset. Anauthentication may include a username, password, one-time password,two-factor authentication, or any other authentication mechanism to gainaccess to a cloud service provider's system. A common interface maydisplay more than one of a vulnerability, an insecure configuration, anindication of a presence of malware, a neglected asset, a data at risk,a lateral movement, and an authentication separately or concurrently foran asset. A display of said information may be ordered and listed in anyorder depending on user preference and input.

An exemplary embodiment may further include a system wherein the commoninterface is configured to display one or more possible attack vectorsreaching the each listed asset. Generating this common interface displaymay include generating a map of an asset to include recordinginformation such as a region identifier, site identifier, datacenteridentifier, physical address, network address, workload name, or anyother identifier which may be acquired via an API provided through acloud service provider's system and demonstrating via a display themyriad attack vectors currently available to an analyzed asset. Displayof the one or more possible attack vectors reaching the each listedasset may be displayed as written text, representative graphicalfigures, or similar method of displaying the one or more possible attackvectors.

Another exemplary embodiment may further include a system wherein thecommon interface is configured to display a recommended mitigationtactic for the each listed asset. A recommended mitigation tactic may begenerated based on historical data of the cybersecurity risk, thevulnerability attributed to the listed asset, or the data contained onthe each listed asset. Mitigation tactics may be selected based on userinput or may be implemented automatically based on the mitigationtactics likelihood of a successful mitigation of the cybersecurity risk.A mitigation tactic may include increased frequency of scanning,heightened access control measures, firewalls and antivirus softwarepatches, increased patch management scheduling, continuous workloadmonitoring, or similar tactics.

In another exemplary embodiment is a system wherein the common interfaceis configured to display one or more workload metrics associated withthe each listed asset. Workload metrics may be a statisticalrepresentation of the current performance of the workload, the capacityfor additional processing of the workload, and the historicalperformance of the workload based on statistical trend.

Another exemplary embodiment may include a system wherein the at leastone processor is further configured to provide a cybersecurity reportfor the each listed asset. A cybersecurity report may be generated byscanning system 101 following a complete scan of an analyzed asset, andmay include a snapshot of one or more of the number of totalcybersecurity threats to a listed asset, number of cybersecurity threatsmitigated by recent performance, methods of cybersecurity riskmitigation in the listed asset, rate of cybersecurity threats detectedin the listed asset, and possibility of failed cybersecurity mitigationtactics based on the frequency and nature of the historicalcybersecurity threats. Data collected to generate a cybersecurity reportmay include, among many things, operating system packages, installedsoftware applications, libraries, and program language libraries such asJava archives, Python packages, Go modules, Ruby gems, PHP packages, andNode.js modules, other software applications, library versions, softwareversions, and other identifying characteristics of software andoperating systems, lists of users of each system or device (e.g.,virtual machines 107A-D), each system's or device's services, passwordhashes, and application-specific configurations for software/servicessuch as Apache, Nginx, SSH, and other services, bugs or otherconfiguration risks, malware scan results, passwords, scripts, shellhistory, repositories, or other data that may contain passwords, cloudaccess keys, SSH keys, or other key/password/access information thatprovide unchecked access to important resources.

In another embodiment, a system may include the at least one processoris configured to identify a risk level distribution among the listedassets. The at least one processor may be configured to list risk leveldistribution by highest level of risk, lowest level of risk, or largestnumber of cybersecurity risks attributed among the listed assets. A risklevel may be high if the web service is connected to the Internet (e.g.,has at least one public port forwarded through a firewall to the webservice, is able to be accessed through a load balancer, is able to beaccessed via reverse proxy). A risk level may be medium risk if the webservice is only accessible internally (e.g., because of firewallconfiguration). A risk level may be low risk if access to the web serveris blocked by a configuration of cloud infrastructure 106.

Another exemplary embodiment may include a system wherein the at leastone processor is configured to receive a search query for a specificrisk. A search query may be input by type of risk, name of a risk, oranother semi-unique manner of identifying a specific cybersecurity risk.A search may be initiated by end user operating user device 102, by amaintainer or administrator of an analyzed asset, or by a virtualmachine associated with operating scanning system 101, A search may beinitiated by inputting a number of inputs, to include keywords, phrases,file type, or similar identifiers unique or semi-unique to a givencybersecurity risk. Upon initiating a search, the results generated bythe search may be stored in the analyzed asset, transmitted to theoperator of a processor running side scanning system 101, or generatedfor review by an end user operating user device 102. The search anddisplay of a specific risk may be based on historical trends ofcybersecurity risks in the listed asset, severity of cybersecurity riskto a listed asset, or a historical search for past cybersecurity threatsto a listed asset.

Another embodiment may include a system wherein the at least oneprocessor is configured to identify one or more assets vulnerable to thespecific risk. For instance, a processor operating scanning system 101may be configured to perform a scan of a set of one or more assets withpotential exposure to a given risk, and upon identifying vulnerablepathways for an attack vector to reach a set of identified assets, maygenerate a list of assets that are potentially or currently exposed toone or more specific risk. Assets vulnerable to a specific risk may bedetermined to be vulnerable based on the type of the specific risk, theexistence of specific risks in adjacent or similar workloads, andrelated risks that may also cause an asset to be vulnerable based on thespecific risk determined.

In another embodiment is a method for providing comprehensive cloudenvironment risk inventory visualization in a graphical user interfacecomprising causing a display to present a plurality of asset categories(step 1101). The method may include the use of a graphical userinterface system and may include systems similar in appearance andfunctionality to Microsoft Windows, Mac OS, Ubuntu Unity, Gnome Shell,Android, Apple iOS, Blackberry OS, Windows 10 Mobile, PalmOS-Web OS, orFirefox OS. For example, cloud infrastructure 106 may be the cloudenvironment consisting of virtual machines 107A-107D, databases109A-109D, storage 111A-111D, keystores 113A-113D, and load balancer115, and the cloud-based storage volume may be contained in storage111A-111D. The cloud environment may include service provided by a thirdparty such as Amazon Web Services, Microsoft Azure, Google Cloud,Alibaba Cloud, IBM Cloud, Oracle, Salesforce, SAP, or similar service.Visualizations provided by the above system may include graphical,sequential, or multi-dimensional displays of risk inventories. Forexample, cloud infrastructure 106 may be the cloud environmentconsisting of virtual machines 107A-107D, databases 109A-109D, storage111A-111D, keystores 113A-113D, and load balancer 115, and thecloud-based storage volume may be contained in storage 111A-111D.

One of several embodiments may include a method for providingcomprehensive cloud environment risk inventory visualization in agraphical user interface comprising receiving, via an input device, aselection of a particular asset category. A method may include apersonal computer, tablet, smartphone, or virtual machine. A processormay include one or more integrated circuits (IC), includingapplication-specific integrated circuit (ASIC), microchips,microcontrollers, microprocessors, all or part of a central processingunit (CPU), graphics processing unit (GPU), digital signal processor(DSP), field-programmable gate array (FPGA), server, virtual server, orother circuits suitable for executing instructions or performing logicoperations. A selection of one or more asset categories may be receivedand updated as new visualizations are developed based on the currentthreats to an asset in that category. Asset categories may be selectedor deselected by an end user. Once a particular asset category isselected, it may be added to a list of selected asset categories with alist for deselected categories as well. The list of selected assetcategories may organized per category or may be compiled to include allcurrent threats in a comprehensive selected asset threat list.

Another embodiment may include a method for providing comprehensivecloud environment risk inventory visualization in a graphical userinterface comprising causing the display to present a list of assets inthe selected category that have cybersecurity risks (step 1105). Adisplay may be graphical, sequential, or multi-dimensional. A list ofselected categories may include at least one of an account category, acontainer category, a database category, an image category, a containercategory, a managed service category, a messaging service category, amonitoring category, a network category, a storage category, a usercategory, a access category, a virtual machine category, or a serverlesscategory. When an asset in a selected category has a cyber security riskassociated with it, the asset may appear in a list of all listedcategories having a cyber security risk associated with it, and may beorganized by individual category, type of cyber security risk, or somecombination or sequential ordering methods based on the informationavailable to the processor and its end user.

Another embodiment may include a method for providing comprehensivecloud environment risk inventory visualization in a graphical userinterface comprising retrieving workload component cybersecurity riskinformation 307A for each listed asset. When a category of assets isselected, a processor may be configured to order those assets accordingto available cybersecurity risk information available to said processor,and may organize by type of risk, type of asset, or similar type ofsequentialization. Cybersecurity risk information may be determined fromhistorical threats to the workload component, the current activecybersecurity threats to workload components of certain types, or somecombination of the same.

Another embodiment may include a method for providing comprehensivecloud environment risk inventory visualization in a graphical userinterface comprising retrieving cloud component cybersecurity riskinformation 307B. Cloud component cybersecurity risk information mayinclude identification of the risk based on a semi-unique identifier,the nature of the risk, the likelihood of the risk, or the severity ofthe risk to each listed asset. Cybersecurity risk information to a cloudcomponent may be determined from historical threats within the cloudenvironment 106, current active cybersecurity threats to similarworkload components in the cloud environment 106 or the level of risk toassets within the cloud environment 106, as outlined above.

Another embodiment may include a method for providing comprehensivecloud environment risk inventory visualization in a graphical userinterface comprising causing the display to present a common interface309 providing access to the workload component cybersecurity riskinformation and cloud component cybersecurity risk information. Thecommon interface may be configured to access component cybersecurityrisk information based on the nature of the risk, the likelihood of therisk, or the severity of the risk to the component. On the same or asimilar and related interface, a display may present cloud componentcybersecurity risk information based on a semi-unique identifier, thenature of the risk, the likelihood of the risk, or the severity of therisk to each listed asset.

Another embodiment may include a method for providing comprehensivecloud environment risk inventory visualization in a graphical userinterface comprising causing the display to present, in the commoninterface, an interconnection between the workload componentcybersecurity risk information and the cloud component cybersecurityrisk information. The interconnection between workload componentcybersecurity risk information 307A and cloud component cybersecurityrisk information 307B may generate an interface between them 309 and maybe presented as an interconnection between them 311. The commoninterface presented may include direct interconnections between thecomponent cybersecurity risk information and the cloud componentcybersecurity risk information or links from one set of cybersecurityrisk information. For instance, the component cybersecurity riskinformation may include a link to access the cloud componentcybersecurity risk information. Conversely, the cloud componentcybersecurity risk information may include a link to access thecomponent cybersecurity risk information.

In another embodiment, a method may include wherein the plurality ofasset categories include at least one of an account category, anauthentication category, a container category, a database category, animage category, a container category, a managed service category, amessaging service category, a monitoring category, a network category, astorage category, a user category, a access category, a virtual machinecategory, or a serverless category. A category may list the currentlyidentified entities of that category type as described below. An accountcategory may include one or more listed accounts of users of the system.An account category may further include listing of assets based on typeof account associated with that user. A type of account may includeactive user account, passive user account, administrator account,maintainer account, a system account, superuser account, or a guest useraccount.

A container category may include one or more containers currently listedin the system. A container may involve specific versions of programminglanguage runtimes, libraries required to run software, or another methodof packaging applications abstracted from the cloud environment.

A database category may include one or more databases managed andmaintained in relation to the system. Databases may include a NoSQLdatabase, a relational database, a cloud database, a columnar database,a wide column database, a key-value database, an object-orienteddatabase, a hierarchical database, or any other kind of database.Databases may be implemented using ElasticCache, ElasticSearch,DocumentDb, DynamoDB, Neptune, RDS, Aurora, Redshift clusters, Kafkaclusters, or EC2 instances.

An image category may contain one or more images based on image type,size, and content. Images may include images of one or more virtualmachines displayed.

A managed service category may include one or more managed serviceslisted in the above system, to include at least client or customer-ownedsystems being managed by a third party entity.

A messaging service category may include services of users communicatingwith at least one other user such as Google Cloud Pub and Subcommunications, AWS SQS, or similar queues found in Information Systems.

A monitoring category may include centralized or decentralized methodsof security monitoring systems.

A network category may include one or more systems of establishing aform of communicative connectivity between systems, e.g., TCP-IPservices.

A storage category may list one or more methods of data storage, toinclude Direct Attached Storage, Network Attached Storage, SSD FlashDrive Arrays, Hybrid Flash Arrays, Hybrid Cloud Storage, BackupSoftware, Backup Appliances, Cloud Storage, or similar. Storage mayinclude data structures, instructions, or any other data to be containedin a storage medium.

A user category may include one or more users of a given system alongwith identifying information relating to its unique or semi-uniqueidentifier, level of authorized access and permissions, and storagevolumes accessible by said user.

An access category may include one or more levels of access permissionand a listing of users or devices granted access at a given level ofaccess permission to a system.

A virtual machine category may list one or more virtual machinesaccessible to a system and the levels and types of access granted to agiven virtual machine.

Another embodiment may include a method wherein the common interface isconfigured to display information relating to at least one of an assettype, a risk, a region, or an account. A common interface may includethe ability to configure and reconfigure the asset type, risk, region,or account to appear in any order and at multiple formats for displayingthe information relating to those categories.

Another embodiment may include a method wherein the common interface isconfigured to display description for each listed asset. The display ofa description for each listed asset may be listed vertically orhorizontally. The display may be displayed as written text,representative graphical figures, or similar method of displaying theaforementioned types of information for an asset.

Another embodiment may include a method wherein the common interface isconfigured to display at least one of a vulnerability, an insecureconfiguration, an indication of a presence of malware, a neglectedasset, a data at risk, a lateral movement, or an authentication. Avulnerability may include vulnerability data from a vulnerabilitydatabase such as NVD, WPVulnDB, US-CERT, Node.js Security Working Group,OVAL— Red Hat, Oracle Linux, Debian, Ubuntu, SUSE, Ruby AdvisoryDatabase, JVN, Safety DB(Python), Alpine secdb, PHP Security AdvisoriesDatabase, Amazon ALAS, RustSec Advisory Database, Red Hat SecurityAdvisories, Microsoft MSRC, KB, Debian Security Bug Tracker, Kubernetessecurity announcements, Exploit Database, Drupal security advisories,JPCERT. An insecure configuration may include software flaws ormisconfigurations, non-encrypted files, improper file or directorypermissions, unpatched security flaws in server software, enabled oraccessible administrative and debugging functions, administrativeaccount vulnerabilities, SSL certificates and encryption settings notproperly configured, or a similar misconfiguration. Thesemisconfigurations may be discovered by performing a scan, e.g., mayquery devices and systems capable of routing traffic (e.g., loadbalancer 115, routers, switches, firewalls, and proxies) using an APIprovided through a cloud service provider's system to determine networkconfigurations, and may evaluate them against known problematicconfigurations or other configurations. Malware indicated may includeAdware, Botnets, Cryptojacking, Malvertising, Ransomware, RemoteAdministration Tools (RATs), Rootkits, Spyware, Trojans, Virus Malware,Worm Malware, or similar attack vehicles. A neglected asset may includean asset that has been improperly maintained, patched, or similarcybersecurity security measure. A data at risk may include any packet ofdata that may be exposed to a cybersecurity threat. A lateral movementmay include any pathway between assets where a cybersecurity risk cantravel from one affected asset to another affected asset. Anauthentication may include a username, password, one-time password,two-factor authentication, or any other authentication mechanism to gainaccess to a cloud service provider's system. A common interface maydisplay more than one of a vulnerability, an insecure configuration, anindication of a presence of malware, a neglected asset, a data at risk,a lateral movement, and an authentication separately or concurrently foran asset. A display of said information may be ordered and listed in anyorder depending on user preference and input.

Another embodiment may include a method wherein the common interface isconfigured to display one or more possible attack vectors reaching theeach listed asset. Generating this common interface display may includegenerating a map of an asset to include recording information such as aregion identifier, site identifier, datacenter identifier, physicaladdress, network address, workload name, or any other identifier whichmay be acquired via an API provided through a cloud service provider'ssystem and demonstrating via a display the myriad attack vectorscurrently available to an analyzed asset. Display of the one or morepossible attack vectors reaching the each listed asset may be displayedas written text, representative graphical figures, or similar metho ofdisplaying the one or more possible attack vectors.

Another embodiment may include a method wherein the common interface isconfigured to display a recommended mitigation tactic for the eachlisted asset. A recommended mitigation tactic may be generated based onhistorical data of the cybersecurity risk, the vulnerability attributedto the listed asset, or the data contained on the each listed asset.Mitigation tactics may be selected based on user input or may beimplemented automatically based on the mitigation tactics likelihood ofa successful mitigation of the cybersecurity risk. A mitigation tacticmay include increased frequency of scanning, heightened access controlmeasures, firewalls and antivirus software patches, increased patchmanagement scheduling, continuous workload monitoring, or similartactics.

Another embodiment may include a method wherein the common interface isconfigured to display one or more workload metrics associated with theeach listed asset. Workload metrics may be a statistical representationof the current performance of the workload, the capacity for additionalprocessing of the workload, and the historical performance of theworkload based on statistical trend.

Another embodiment may include a non-transitory computer readable mediumstoring instructions that, when executed by at least one processor, areconfigured to cause the at least one processor to perform operations formatching keys with compute resources, the operations comprising causinga display to present a plurality of asset categories 301. A pluralitymay include at least one asset category to be displayed. Assetcategories may include at least one of an account category, a containercategory, a database category, an image category, a container category,a managed service category, a messaging service category, a monitoringcategory, a network category, a storage category, a user category, aaccess category, a virtual machine category, or a serverless category.

Another embodiment may include a non-transitory computer readable mediumstoring instructions that, when executed by at least one processor, areconfigured to cause the at least one processor to perform operations formatching keys with compute resources, the operations comprisingreceiving, via an input device, a selection of a particular assetcategory (step 1103). An input device may include a personal computer,tablet, smartphone, or virtual machine. A processor may include one ormore integrated circuits (IC), including application-specific integratedcircuit (ASIC), microchips, microcontrollers, microprocessors, all orpart of a central processing unit (CPU), graphics processing unit (GPU),digital signal processor (DSP), field-programmable gate array (FPGA),server, virtual server, or other circuits suitable for executinginstructions or performing logic operations. A selection of one or moreasset categories may be received and updated as new visualizations aredeveloped based on the current threats to an asset in that category.Asset categories may be selected or deselected by an end user. Once aparticular asset category is selected, it may be added to a list ofselected asset categories with a list for deselected categories as well.The list of selected asset categories may organized per category or maybe compiled to include all current threats in a comprehensive selectedasset threat list.

Another embodiment may include a non-transitory computer readable mediumstoring instructions that, when executed by at least one processor, areconfigured to cause the at least one processor to perform operations formatching keys with compute resources, the operations comprising causingthe display to present a list of assets in the selected category thathave cybersecurity risks (step 1105). A display may be graphical,sequential, or multi-dimensional. A list of selected categories mayinclude at least one of an account category, a container category, adatabase category, an image category, a container category, a managedservice category, a messaging service category, a monitoring category, anetwork category, a storage category, a user category, a accesscategory, a virtual machine category, or a serverless category. When anasset in a selected category has a cyber security risk associated withit, the asset may appear in a list of all listed categories having acyber security risk associated with it, and may be organized byindividual category, type of cyber security risk, or some combination orsequential ordering methods based on the information available to theprocessor and its end user.

Another embodiment may include a non-transitory computer readable mediumstoring instructions that, when executed by at least one processor, areconfigured to cause the at least one processor to perform operations formatching keys with compute resources, the operations comprisingretrieving workload component cybersecurity risk information for eachlisted asset (step 1107A). When a category of assets is selected, aprocessor may be configured to order those assets according to availablecybersecurity risk information available to said processor, and mayorganize by type of risk, type of asset, or similar type ofsequentialization. Cybersecurity risk information may be determined fromhistorical threats to the workload component, the current activecybersecurity threats to workload components of certain types, or somecombination of the same.

Another embodiment may include a non-transitory computer readable mediumstoring instructions that, when executed by at least one processor, areconfigured to cause the at least one processor to perform operations formatching keys with compute resources, the operations comprisingretrieving cloud component cybersecurity risk information for eachlisted asset (step 1107B). Cloud component cybersecurity riskinformation may include identification of the risk based on asemi-unique identifier, the nature of the risk, the likelihood of therisk, or the severity of the risk to each listed asset. Cybersecurityrisk information to a cloud component may be determined from historicalthreats within the cloud environment 106, current active cybersecuritythreats to similar workload components in the cloud environment 106 orthe level of risk to assets within the cloud environment 106, asoutlined above.

Another embodiment may include a non-transitory computer readable mediumstoring instructions that, when executed by at least one processor, areconfigured to cause the at least one processor to perform operations formatching keys with compute resources, the operations comprising causingthe display to present a common interface providing access to theworkload component cybersecurity risk information and cloud componentcybersecurity risk information for each listed asset (step 1109). Thecommon interface may be configured to access component cybersecurityrisk information based on the nature of the risk, the likelihood of therisk, or the severity of the risk to the component. On the same or asimilar and related interface, a display may present cloud componentcybersecurity risk information based on a semi-unique identifier, thenature of the risk, the likelihood of the risk, or the severity of therisk to each listed asset.

Another embodiment may include a non-transitory computer readable mediumstoring instructions that, when executed by at least one processor, areconfigured to cause the at least one processor to perform operations formatching keys with compute resources, the operations comprising causingthe display to present, in the common interface, an interconnectionbetween the workload component cybersecurity risk information and thecloud component cybersecurity risk information (step 1111). Theinterconnection between workload component cybersecurity riskinformation (step 1107A) and cloud component cybersecurity riskinformation (step 1107B) may generate an interface between them (step1109) and may be presented as an interconnection between them (step1111). The common interface presented may include directinterconnections between the component cybersecurity risk informationand the cloud component cybersecurity risk information or links from oneset of cybersecurity risk information. For instance, the componentcybersecurity risk information may include a link to access the cloudcomponent cybersecurity risk information. Conversely, the cloudcomponent cybersecurity risk information may include a link to accessthe component cybersecurity risk information.

In some embodiments, a processor may cause a display of one or morerisks aggregated in the same visualization. FIG. 12 is a schematic blockdiagram illustrating an exemplary embodiment of a visual representationof displaying aggregated cybersecurity risk information, consistent withdisclosed embodiments. A visualization may be generated from one or moresources based on scanning system 101. For example, a visual display mayinclude a cloud provider visualization 1201, displaying where themultiple sources of data may be derived from. A cloud service providermay include services such as Cloudflare, Amazon Web Services, GoogleCloud, IBM Cloud, Oracle Cloud, Microsoft Azure, or similar. This isfurther displayed via a communicative connection through an access port1203 to a data server 1205.

Data server 1205 may include servers such as 109A-D. Data server 1205may then display risk information that may be communicatively passedthrough web server 1207, demonstrating one or more possible sources ofthe one or more cybersecurity risk information. Data server 1205 may becommunicatively connected to a web server 1207 (through access port1203, which may be the same or a different port from port 1203 betweencloud service provider 1201 and data server 1205), which can then becommunicatively connected to one or more users via user access points1209. This may include, among other things, user access that may beverified or validated via a credential 1211. Each of these connectionsmay demonstrate one or more risk paths that may be exploited in a singleview to allow for prioritization of threats and analysis of possibleusers who may exploit those risks and vulnerabilities, as discussedabove. This may allow an administrator to prioritize risks to a givenstorage volume as well as assess lateral storage volumes that may besimilarly risked based on the assessed threats in a single image.

FIG. 13 is a schematic block diagram illustrating an exemplaryembodiment of a visual representation of a flow path for aggregated riskinformation, consistent with disclosed embodiments. In anotherembodiment, a processor may be configured to display a flow path ofaggregated risk information. In one view, a displayed visualization mayinclude user access 1301, which displays risk information such asservice vulnerability 1303 and an insecure private key 1303. Thesevulnerabilities or risks may be displayed to an administrator viadeveloper server 1307 to an administrator through administrator access1309. As previously discussed, this will allow an administrator tovisualize myriad risks to a storage volume in a single view that willallow an administrator to prioritize risks and analyze possibleexploiters of this risk information on lateral systems and storagevolumes.

In another embodiment, risk information may be shown in one or moreviews. This may involve a risk path similar to the exemplary embodimentof FIG. 13. In an exemplary embodiment, in a single visualization datafrom multiple sources may be displayed. This may involve identifyingrisk information such as the origin of the risk and potential exploitersof a risk. In some embodiments, this visualization may be done for aspecific risk. In another embodiment, this visualization may be done fora combination of risks.

Disclosed embodiments may include any one of the followingbullet-pointed features alone or in combination with one or more otherbullet-pointed features, whether implemented as a method, by at leastone processor, and/or stored as executable instructions on nontransitory computer readable media:

-   -   establishing a trusted relationship between a source account in        a cloud environment and a scanner account;    -   using the established trust relationship, utilize at least one        cloud provider API to identify workloads in the source account;    -   using the at least one cloud provider API to query a        geographical location of at least one of the identified        workloads;    -   receiving an identification of the geographic location;    -   using the cloud provider APIs to access block storage volumes of        the at least one workload;    -   determining a file-system of the at least one workload;    -   mounting the block storage volumes on a scanner based on the        determined file-system;    -   activating a scanner at the geographic location;    -   reconstructing from the block storage volumes a state of the        workload; and    -   assessing the reconstructed state of the workload to extract        insights.    -   wherein the geographic location includes an identifier of a        physical site.    -   wherein mounting includes selecting a driver corresponding to        the determined file system.    -   wherein the at least one processor is further configured to        deploy a scanner at the geographical location.    -   wherein the identification of the geographic location comprises        an identification of a data center, at least one of a data        center name, Internet Protocol (IP) address, name of the cloud        provider, or a unique identity.    -   wherein the reconstructed state of the workload includes at        least two of an indication of an installed application, a        version of an installed application, an operating system        configuration, an application configuration, a profile        configuration, a log, or a database content;    -   wherein the at least one processor is further configured to        update the reconstructed state of the workload based on at least        one change to the block storage volumes.    -   wherein the insights comprise at least one of a vulnerability        associated with the workload or a composition of installed        applications associated with the workload.    -   wherein to mount the block storage volumes on the scanner, the        at least one processor is configured to create a snapshot of the        block storage volumes;    -   wherein to mount the block storage volumes on the scanner, the        at least one processor is configured to mount the snapshot of        the block storage volumes on the scanner    -   wherein the at least one processor is further configured to        encrypt the snapshot of the block storage volumes;    -   wherein the at least one processor is further configured to        mount the encrypted snapshot of the block storage volumes on the        scanner;    -   using a cloud provider API, access a block storage volume of a        workload maintained in a cloud storage environment;    -   identifying an installed software application in the accessed        block storage volume;    -   analyzing the identified installed software application to        determine an associated software version;    -   accessing a data structure of known software vulnerabilities for        a plurality of versions of software applications;    -   performing a lookup of the identified installed software version        in the data structure to identify known vulnerabilities; and    -   performing at least one of query the cloud provider API to        determine network accessibility information related to the        workload, identify at least one port on which the vulnerable        application is accessible, use network accessibility information        and at least one port to identify one or more vulnerabilities        susceptible to attack from outside the workload.    -   implementing a remedial action in response to the identified one        or more vulnerabilities.    -   wherein the remedial measure includes transmitting an alert to a        device associated with an administrator.    -   wherein querying the cloud provider API to determine network        accessibility information related to the workload further        comprises examining data sources associated with the workload    -   wherein querying the cloud provider API to determine network        accessibility information related to the workload further        comprises determining the network accessibility information        based on the examined data sources.    -   wherein querying the cloud provider API to determine network        accessibility information related to the workload further        comprises: wherein the network accessibility information        includes at least one of: data from an external data source,        cloud provider information, or at least one network capture log.    -   identifying the installed software application comprises        extracting data from at least one of operating system packages,        libraries, or program language libraries;    -   identifying the installed software application comprises        identifying the installed software application based on the        extracted data;    -   identifying a version of the installed software application;    -   wherein the identified installed software application includes        one or more scripts;    -   wherein the data structure includes aggregated vulnerability        data;    -   wherein the aggregated vulnerability data includes data from one        or more third-party vendors;    -   wherein the aggregated vulnerability data includes data        collected by a scanner;    -   wherein the aggregated vulnerability data includes at least one        of an advisory, an exploit, a security announcement, or a known        bug.    -   querying the cloud provider API to determine network        accessibility information related to the workload further        comprises: wherein the network accessibility information        includes at least one of: data from an external data source,        cloud provider information, or at least one network capture log.    -   accessing at least one cloud provider API to determine a        plurality of entities capable of routing traffic in a virtual        cloud environment associated with a target account containing        the workload;    -   querying the at least one cloud provider API to determine at        least one networking configuration of the entities;    -   building a graph connecting the plurality of entities based on        the networking configuration;    -   accessing a data structure identifying services publicly        accessible via the internet and capable of serving as an        internet proxy;    -   integrating the identified services into the graph;    -   traversing the graph to identify at least one source originating        via the internet and reaching the workload; and    -   outputting a risk notification associated with the workload.    -   wherein the plurality of entities includes a virtual network        appliance.    -   wherein the virtual network appliance is at least one of a load        balancer, a firewall, a proxy, or a router.    -   wherein the networking configuration is at least one of a        routing configuration, a proxy configuration, a load balancing        configuration, a firewall configuration, or a VPN configuration.    -   wherein the graph includes a data structure sequentially        connecting entities.    -   wherein the graph includes directional vectors indicating        directions of dataflow.    -   wherein building the graph comprises identifying individual        entities as nodes    -   wherein building the graph comprises connecting the nodes.    -   wherein the graph includes port numbers associated with the        workload.    -   wherein the graph includes a path from the at least one source        to the workload.    -   utilizing a cloud provider API to access a block storage volume        of a workload maintained on a target account in a target system        of a cloud storage environment;    -   utilizing a scanner at a location of the block storage volume        and on a secondary system other than the target system;    -   scanning the block storage volume for malicious code, using the        secondary system;    -   identifying malicious code based on the scan; and    -   outputting from the secondary system, a notification of a        presence of malicious code in the target system.    -   wherein the location of the block storage volume includes at        least one of: the target account, a secondary system account, a        cloud provider account, or a third party account.    -   wherein scanning the block storage volume includes scanning        disk-backed memory.    -   wherein the disk-backed memory includes at least one of a page        file or a cache file.    -   wherein the secondary system includes at least one of a virtual        machine, a container, or a serverless function.    -   wherein the secondary system has an operating system different        from an operating system of the target account.    -   wherein the malicious code includes a rootkit.    -   wherein utilizing a scanner includes suspending an operation of        the scanner after the scan of the block storage volume.    -   wherein utilizing a scanner includes modifying a pre-utilized        scanner at the location of the block storage volume based on        information related to the target account to obtain a modified        scanner;    -   wherein utilizing a scanner includes utilizing the modified        scanner.    -   identifying assets in a cloud environment;    -   identifying risks associated with each of the identified asset;    -   identifying relationships between at least some of the        identified assets, the relationships including at least one of a        trust, a network connectivity, or a mechanism of network        proxying;    -   receiving an identification of a specific asset under        investigation;    -   performing a forward analysis of the specific asset under        investigation to identify at least one possible attack vector        reaching the specific asset via a network outside the cloud        environment;    -   performing a backward analysis of the specific asset to identify        at least one exposure risk to one or more assets that is in a        downstream of the specific asset, wherein the at least one        exposure risk includes an identification of an exposed asset, an        entry point to the exposed asset, and a lateral movement risk        associated with the exposed asset; and    -   outputting a signal to cause on a display to present a        presentation of forward and backward paths associated with the        specific asset, thereby enabling visualization of a plurality of        entry points and lateral movement risks associated with the        plurality of entry points.    -   wherein the network outside the cloud environment includes the        Internet.    -   wherein the assets in the cloud environment include at least one        of: a virtual machine, a network appliance, a storage appliance,        a compute instances, or an engine instance.    -   wherein identifying the assets in a cloud environment includes        identifying the assets based on at least one of: an identity and        access management policy, an organization policy, or an access        policy.    -   wherein the presentation of the forward and backward paths        indicates alternative paths connecting between the specific        asset and an upstream asset or a downstream asset.    -   wherein the visualization includes a presentation of the        alternative paths.    -   wherein the presentation of the forward and backward paths        indicates port numbers for each pathway.    -   wherein the visualization of the entry points indicates at least        one entry point at risk.    -   monitoring network activities of the assets in a cloud        environment.    -   detecting detect a potential risk associated with the specific        asset based on the monitored network activities.    -   detecting a potential risk associated with the specific asset        based on a network activity of the specific asset.    -   detecting a potential risk associated with the specific asset        based on a network activity of an upstream asset of the specific        asset.    -   detecting a potential risk associated with the specific asset        based on a network activity of a downstream asset of the        specific asset.    -   analyzing a cloud environment to identify a plurality of keys to        the compute resources in the cloud environment;    -   performing a cryptographic analysis on the plurality of keys to        identify a first set of fingerprints that uniquely identify each        of the plurality of keys, the first set of fingerprints being        non-functional;    -   analyzing trust configurations of the compute resources to        identify a second set of fingerprints for each of the compute        resources; and    -   comparing the first set of fingerprints with the second set of        fingerprints to match keys with the compute resources without        using the keys to access the compute resources.    -   wherein the plurality of keys are stored in at least one        workload.    -   wherein at least one of the first set of fingerprints is not        identical to any key of the plurality of keys.    -   wherein at least one of the plurality of keys includes at least        one of a password, a script containing a password, a private        component of a private-public key pair, a cloud key, or an        Secure Shell (SSH) key.    -   testing validity of at least one of the plurality of keys.    -   analyzing a multi-machine interaction in the cloud environment        using the first set of fingerprints.    -   analyzing the multi-machine interaction includes comparing the        first set of fingerprints with the second set of fingerprints.    -   analyzing a multi-machine interaction in the cloud environment        using the plurality of keys.    -   accessing a primary account maintained in a cloud environment;    -   receiving information defining a structure of the primary        account, wherein the structure includes a plurality of assets,        and wherein the information excludes raw data of the primary        account;    -   deploying, inside the primary account or inside a secondary        account for which trust has been established with the primary        account, at least one ephemeral scanner configured to scan at        least one block storage volume and to output metadata defining        the at least one block storage volume, the output excluding raw        data of the primary account;    -   receiving a transmission of the metadata from the at least one        ephemeral scanner, wherein the transmission excludes raw data of        the primary account;    -   analyzing the received metadata to identify a plurality of        cybersecurity vulnerabilities;    -   correlating each of the identified plurality of cybersecurity        vulnerabilities with one of the plurality of assets; and    -   generating a report correlating the plurality of cybersecurity        vulnerabilities with the plurality of assets.    -   wherein defining the at least one block storage volume includes        presenting risk data without sharing consumer data or data that        was used to identify the risk data.    -   wherein the metadata defining the at least one block storage        volume includes at least one of: an indication of an installed        application, a version of an installed application, an operating        system configuration, an application configuration, or a profile        configuration.    -   receiving a transmission of updated metadata defining the at        least one block storage volume in response to at least one        change to the at least one block storage volumes.    -   wherein the ephemeral scanner is configured to perform        vulnerability scanning of the at least one block storage volume.    -   wherein the ephemeral scanner is configured to perform        configuration scanning of the at least one block storage volume.    -   wherein the ephemeral scanner is configured to perform malware        scanning of the at least one block storage volume.    -   wherein the ephemeral scanner is configured to perform        lateral-movement risk analysis of the at least one block storage        volume.    -   wherein the ephemeral scanner is configured to perform sensitive        information scanning of the at least one block storage volume.    -   wherein the ephemeral scanner is configured to perform container        scanning of the at least one block storage volume.    -   wherein the ephemeral scanner is configured to perform keys and        password scanning of the at least one block storage volume.    -   causing a display to present a plurality of asset categories;    -   receiving, via an input device, a selection of a particular        asset category;    -   causing the display to present a list of assets in the selected        category that have cyber security risks;    -   for each listed asset, retrieving workload component        cybersecurity risk information, and    -   for each listed asset. retrieving cloud component cybersecurity        risk information;    -   for each listed asset, causing the display to present a common        interface providing access to the workload component        cybersecurity risk information and cloud component cybersecurity        risk information; and    -   for each listed asset, causing the display to present, in the        common interface, an interconnection between the workload        component cybersecurity risk information and the cloud component        cybersecurity risk information.    -   wherein the plurality of asset categories include at least one        of an account category, an authentication category, a container        category, a database category, an image category, a container        category, a managed service category, a messaging service        category, a monitoring category, a network category, a storage        category, a user category, a access category, a virtual machine        category, or a serverless category.    -   wherein the common interface is configured to display        information relating to at least one of an asset type, a risk, a        region, or an account.    -   wherein the common interface is configured to display        description for each listed asset.    -   wherein the common interface is configured to display at least        one of a vulnerability, an insecure configuration, an indication        of a presence of malware, a neglected asset, a data at risk, a        lateral movement, or an authentication.    -   wherein the common interface is configured to display one or        more possible attack vectors reaching the each listed asset.    -   wherein the common interface is configured to display a        recommended mitigation tactic for the each listed asset.    -   wherein the common interface is configured to display one or        more workload metrics associated with the each listed asset.    -   wherein the at least one processor is further configured to        provide a cybersecurity report for the each listed asset.    -   wherein the at least one processor is configured to identify a        risk level distribution among the listed assets.    -   receiving a search query for a specific risk; or    -   identifying one or more assets vulnerable to the specific risk.

Other embodiments will be apparent to those skilled in the art fromconsideration of the specification and practice of the disclosedembodiments disclosed herein. It is intended that the specification andexamples be considered as exemplary only, with a true scope and spiritof the disclosed embodiments being indicated by the following claims.

Computer programs based on the written description and methods of thisspecification are within the skill of a software developer. The variousprograms or program modules can be created using a variety ofprogramming techniques. One or more of such software sections or modulescan be integrated into a computer system, non-transitory computerreadable media, or existing software.

Moreover, while illustrative embodiments have been described herein, thescope includes any and all embodiments having equivalent elements,modifications, omissions, combinations (e.g., of aspects across variousembodiments), adaptations or alterations based on the presentdisclosure. The elements in the claims are to be interpreted broadlybased on the language employed in the claims and not limited to examplesdescribed in the present specification or during the prosecution of theapplication. These examples are to be construed as non-exclusive.Further, the steps of the disclosed methods can be modified in anymanner, including by reordering steps or inserting or deleting steps. Itis intended, therefore, that the specification and examples beconsidered as exemplary only, with a true scope and spirit beingindicated by the following claims and their full scope of equivalents.

1-118. (canceled)
 119. A cybersecurity scanner deployment system,comprising: at least one processor configured to: access a primaryaccount maintained in a cloud environment; receive information defininga structure of the primary account, wherein the structure includes aplurality of assets, and wherein the information excludes raw data ofthe primary account; deploy, inside the primary account or inside asecondary account for which trust has been established with the primaryaccount, at least one ephemeral scanner configured to scan at least oneblock storage volume and to output metadata defining the at least oneblock storage volume, the output excluding raw data of the primaryaccount; receive a transmission of the metadata from the at least oneephemeral scanner, wherein the transmission excludes raw data of theprimary account; analyze the received metadata to identify a pluralityof cybersecurity vulnerabilities; correlate each of the identifiedplurality of cybersecurity vulnerabilities with one of the plurality ofassets; and generate a report correlating the plurality of cybersecurityvulnerabilities with the plurality of assets.
 120. The system of claim119, wherein defining the at least one block storage volume includespresenting risk data without sharing consumer data or data that was usedto identify the risk data.
 121. The system of claim 119, wherein themetadata defining the at least one block storage volume includes atleast one of: an indication of an installed application, a version of aninstalled application, an operating system configuration, an applicationconfiguration, or a profile configuration.
 122. The system of claim 119,wherein the at least one processor is further configured to receive atransmission of updated metadata defining the at least one block storagevolume in response to at least one change to the at least one blockstorage volumes.
 123. The system of claim 119, wherein the ephemeralscanner is configured to perform vulnerability scanning of the at leastone block storage volume.
 124. The system of claim 119, wherein theephemeral scanner is configured to perform configuration scanning of theat least one block storage volume.
 125. The system of claim 119, whereinthe ephemeral scanner is configured to perform malware scanning of theat least one block storage volume.
 126. The system of claim 119, whereinthe ephemeral scanner is configured to perform lateral-movement riskanalysis of the at least one block storage volume.
 127. The system ofclaim 119, wherein the ephemeral scanner is configured to performsensitive information scanning of the at least one block storage volume.128. The system of claim 119, wherein the ephemeral scanner isconfigured to perform container scanning of the at least one blockstorage volume.
 129. The system of claim 119, wherein the ephemeralscanner is configured to perform keys and password scanning of the atleast one block storage volume.
 130. A method for cybersecurity scannerdeployment, comprising: accessing a primary account maintained in acloud environment; receiving information defining a structure of theprimary account, wherein the structure includes a plurality of assets,and wherein the information excludes raw data of the primary account;deploying, inside the primary account or inside a secondary account forwhich trust has been established with the primary account, at least oneephemeral scanner configured to scan at least one block storage volumeand to output metadata defining the at least one block storage volume,the output excluding raw data of the primary account; receiving atransmission of the metadata from the at least one ephemeral scanner,wherein the transmission excludes raw data of the primary account;analyzing the received metadata to identify a plurality of cybersecurityvulnerabilities; correlating each of the identified plurality ofcybersecurity vulnerabilities with one of the plurality of assets; andgenerating a report correlating the plurality of cybersecurityvulnerabilities with the plurality of assets.
 131. The method of claim130, wherein defining the at least one block storage volume includespresenting risk data without sharing consumer data or data that was usedto identify the risk data.
 132. The method of claim 130, wherein themetadata defining the at least one block storage volume includes atleast one of: an indication of an installed application, a version of aninstalled application, an operating system configuration, an applicationconfiguration, or a profile configuration.
 133. The method of claim 130,further comprising receiving a transmission of updated metadata definingthe at least one block storage volume in response to at least one changeto the at least one block storage volumes.
 134. The method of claim 130,wherein the ephemeral scanner is configured to perform vulnerabilityscanning of the at least one block storage volume.
 135. The method ofclaim 130, wherein the ephemeral scanner is configured to performconfiguration scanning of the at least one block storage volume. 136.The method of claim 130, wherein the ephemeral scanner is configured toperform malware scanning of the at least one block storage volume. 137.The method of claim 130, wherein the ephemeral scanner is configured toperform lateral-movement risk analysis of the at least one block storagevolume.
 138. A non-transitory computer-readable medium storinginstructions that, when executed by at least one processor, areconfigured to cause the at least one processor to perform operationscomprising: accessing a primary account maintained in a cloudenvironment; receiving information defining a structure of the primaryaccount, wherein the structure includes a plurality of assets, andwherein the information excludes raw data of the primary account;deploying, inside the primary account or inside a secondary account forwhich trust has been established with the primary account, at least oneephemeral scanner configured to scan at least one block storage volumeand to output metadata defining the at least one block storage volume,the output excluding raw data of the primary account; receiving atransmission of the metadata from the at least one ephemeral scanner,wherein the transmission excludes raw data of the primary account;analyzing the received metadata to identify a plurality of cybersecurityvulnerabilities; correlating each of the identified plurality ofcybersecurity vulnerabilities with one of the plurality of assets; andgenerating a report correlating the plurality of cybersecurityvulnerabilities with the plurality of assets. 139.-159. (canceled)